Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1334768446.1123773255800.JavaMail.jira@ajax.apache.org>
Date: Thu, 11 Aug 2005 17:14:15 +0200 (CEST)
From: "Alex Karasulu (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Assigned: (DIREVE-180) Problem with the shutdown sequence.
In-Reply-To: <114504772.1120817775366.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ 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

-- 
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