directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Commented: (DIREVE-330) Allow the installation of the shutdown handler to be optional for embedded servers
Date Sun, 29 Jan 2006 05:36:34 GMT
    [ http://issues.apache.org/jira/browse/DIREVE-330?page=comments#action_12364361 ] 

Alex Karasulu commented on DIREVE-330:
--------------------------------------

Simon we certainly do need to implement this option for not registering the shutdown hook.
 I will add this to the core startup configuration which the XML file will also support. 
Now the GracefulShutdown mechanism may play into the way the stopService() method should be
implemented since this extended request blocks until all clients are properly notified with
a GracefulDisconnect followed by a NoticeOfDisconnect (if they don't understand the GracefulDisconnect).
 This also gives operations in progress a chance to complete.  I have no idea how this interaction
is achieved however I will investigate this.  

For the time being let me just add a configuratioin parameter for you so this hook does not
get in your way.  Sorry for taking so long to get to this issue.

Alex


> Allow the installation of the shutdown handler to be optional for embedded servers
> ----------------------------------------------------------------------------------
>
>          Key: DIREVE-330
>          URL: http://issues.apache.org/jira/browse/DIREVE-330
>      Project: Directory Server
>         Type: Improvement
>   Components: server main
>     Versions: 0.9.4
>  Environment: Windows/UNIX JDK 1.4 - Embedded server within JBoss
>     Reporter: Simon Temple
>     Assignee: Alex Karasulu
>     Priority: Minor

>
> I am using the directory embedded in JBoss.  When we shutdown JBoss our
> application services need to remove certain entries from the directory.
> Unfortunately the shutdown handler in DefaultDirectoryServices closes Eve
> out before we get chance to finish and we get errors:
> org.apache.ldap.common.exception.LdapServiceUnavailableException:
> Context operation unavailable when invoked after Eve provider has been
> shutdown
> When our services finally stop, we stop the directory using the
> ShutdownConfiguration class so we don't really need the additional shutdown
> thread.
> I've commented out the shutdown hook code and our server is now behaving
> how we want but I don't like running with patched source...

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