directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Resolved: (DIREVE-180) Problem with the shutdown sequence.
Date Fri, 12 Aug 2005 07:43:54 GMT
     [ http://issues.apache.org/jira/browse/DIREVE-180?page=all ]
     
Trustin Lee resolved DIREVE-180:
--------------------------------

    Fix Version: 0.9.2
     Resolution: Fixed

Yes, Tony's patch is already applied to trunk.  I added some check code, too.

> Problem with the shutdown sequence.
> -----------------------------------
>
>          Key: DIREVE-180
>          URL: http://issues.apache.org/jira/browse/DIREVE-180
>      Project: Directory Server
>         Type: Bug
>     Reporter: Tony Blanchard
>     Assignee: Trustin Lee
>     Priority: Minor
>      Fix For: 0.9.2

>
> In AbstractContextFactory:getInitialContext
> 1-gets the DefaultContextFactoryService and asks it to shutdown.
>     1-1-DefaultContextFactoryService shuts down and reset startupConfiguration field
> 2- asks the DefaultContextFactoryService to getInitialContext and uses checkSecuritySettings
before returning DeadContext
>   2-1 checkSecuritySettings uses startupConfiguration field and throws NullPointerException...
> To pass this problem I made a temporary change to the DefaultContextFactoryService by
commenting the startupConfiguration = null; in the finally block of shutdown() method.
> Instead, I putted this code in the getJNDIContext method  :
> "checkSecuritySettings[...]
> if (!started)
> {
>    startupConfiguration = null; //New code
>   return DeadContext();
> }"
>  I made this because using afterShutdown hook is to early in sequence and I think only
an authentified guy should shutdown the server...
> On more thing is that it seams there is no test about shutdowning server and then make
a call to an operation on it to produce an exception.
> Best regards,
> Tony

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message