[jira] Closed: (DIRSERVER-322) Problem with the shutdown sequence.

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-322.
---------------------------------------


Closing all issues created in 2005 and before which are marked resolved

> Problem with the shutdown sequence.
> -----------------------------------
>
>                 Key: DIRSERVER-322
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-322
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Tony Blanchard
>         Assigned To: Trustin Lee
>            Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.