Problem with the shutdown sequence.

• Key: DIRSERVER-322
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Trustin Lee
• Reporter: Tony Blanchard

Description

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

Comments

[Alex Karasulu]

Trustin can you take a look into this if it has not been corrected already. I suspect this issue is over and done with and can just be closed. Perhaps Tony can comment on this.

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

[Emmanuel Lecharny]

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