directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-2060) Bind not working after server startup
Date Tue, 21 Apr 2015 23:11:00 GMT

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

Stefan Seelmann commented on DIRSERVER-2060:
--------------------------------------------

The problem is in AuthenticationInterceptor we use a HashSet which holds the authenticators,
and for each JVM start (and probaly JVM version and platform) the "order" is different.

Another issue is that register() is called twice, once with null DirectoryService and once
with the instance.

> Bind not working after server startup
> -------------------------------------
>
>                 Key: DIRSERVER-2060
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2060
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Stefan Seelmann
>            Priority: Blocker
>             Fix For: 2.0.0-M20
>
>
> When starting the server sometimes it is not possible to bind to the server. In that
case the following error is returned to the client:
> {noformat}
> INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=admin,ou=system
> {noformat}
> Same error is reproducable in UberJarMainTest, it fails sporadically on my machine (Linux)
and on Jenkins (https://builds.apache.org/view/A-D/view/Directory/job/dir-apacheds-ubuntu-deploy/1680/org.apache.directory.server$apacheds-service/testReport/org.apache.directory.server/UberJarMainTest/serviceInstanceTest/)



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

Mime
View raw message