Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Sun, 9 Oct 2016 23:30:20 +0000 (UTC)
From: "Shawn McKinney (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.13010873.1476048626000.778035.1476055820517@Atlassian.JIRA>
In-Reply-To: <JIRA.13010873.1476048626000@Atlassian.JIRA>
References: <JIRA.13010873.1476048626000@Atlassian.JIRA> <JIRA.13010873.1476048626043@arcas>
Subject: [jira] [Commented] (FC-192) [ fortress-core ] problems with config
 system
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 09 Oct 2016 23:30:22 -0000


    [ https://issues.apache.org/jira/browse/FC-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15560824#comment-15560824 ] 

Shawn McKinney commented on FC-192:
-----------------------------------

and changed UserP's constructors to use non-static for UserDAO:

    private UserDAO uDao;
    UserP()
    {
    	uDao = new UserDAO();
    }

running tests now, seems to work fine.

> [ fortress-core ] problems with config system
> ---------------------------------------------
>
>                 Key: FC-192
>                 URL: https://issues.apache.org/jira/browse/FC-192
>             Project: FORTRESS
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>            Reporter: Shawn McKinney
>            Assignee: Shawn McKinney
>             Fix For: 2.0.0-RC1
>
>
> Problem appeared recently with fortress-web.  One of the config variables, user.objectClass, could not be found causing a problem with the fortress load utility's user create.  
> The error from log is below.  Notice the values of the user's object class has 'null' for 2nd value.
> After troubleshooting I discovered the problem occurred due to a recent change of UserDAO var decl in UserP to a non-static:
> // TODO: Fixme - This variable must remain static for now or the config bootstrap doesn't work right:
>     private static UserDAO uDao;
> After returning the value to static as shown the problem went away.
> This is fragile and needs to be fixed so that making simple changes like this don't break the config system.
> Error:
>  [startAnt] [FortressAdmin] DEBUG - 09 Oct 2016 15:59:27,297 - RegExUtil                  - safeText can't find safeText regular expression pattern.  Check your Fortress cfg
>  [startAnt] [FortressAdmin] DEBUG - 09 Oct 2016 15:59:27,298 - Config                     - getProperty name [user.root] value [ou=People,dc=example,dc=com]
>  [startAnt] [FortressAdmin] ******* OBJECT CLASS=top
>  [startAnt] [FortressAdmin] ******* OBJECT CLASS=null
>  [startAnt] [FortressAdmin] ******* OBJECT CLASS=ftUserAttrs
>  [startAnt] [FortressAdmin] ******* OBJECT CLASS=ftProperties
>  [startAnt] [FortressAdmin] ******* OBJECT CLASS=ftMods
>  [startAnt] [FortressAdmin] ******* OBJECT CLASS=extensibleObject
>  [startAnt] [FortressAdmin] DEBUG - 09 Oct 2016 15:59:27,298 - Config                     - getProperty name [pwpolicy.root] value [ou=Policies,dc=example,dc=com]
>  [startAnt] [FortressAdmin] ****************************    pwpolicy.root=ou=Policies,dc=example,dc=com
>  [startAnt] [FortressAdmin] WARN  - 09 Oct 2016 15:59:27,299 - FortressAntTask            - addUsers userId [test7] caught SecurityException={}
>  [startAnt] [FortressAdmin] org.apache.directory.fortress.core.CreateException: create userId [test7] caught LDAPException=objectClass: value #1 invalid per syntax
>  [startAnt] [FortressAdmin] 	at org.apache.directory.fortress.core.impl.UserDAO.create(UserDAO.java:569)
>  [startAnt] [FortressAdmin] 	at org.apa


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)