directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Blanchard <blt...@wanadoo.fr>
Subject Re: [jira] Assigned: (DIREVE-180) Problem with the shutdown sequence.
Date Fri, 12 Aug 2005 08:19:02 GMT
I did nothing on it while it was a temporary correction for my personal 
use and for JIRA users.
As I did not know the design model, I just gave this clue to find what 
was wrong with the shutdown sequence.


Hope this help.
Tony

Alex Karasulu (JIRA) a écrit :

>     [ http://issues.apache.org/jira/browse/DIREVE-180?page=all ]
>
>Alex Karasulu reassigned DIREVE-180:
>------------------------------------
>
>    Assign To: Trustin Lee  (was: 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.
>
>  
>
>>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
>>    
>>
>
>  
>
>>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
>>    
>>
>
>  
>



Mime
View raw message