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 Wed, 25 Jan 2006 17:52:09 GMT
    [ http://issues.apache.org/jira/browse/DIREVE-330?page=comments#action_12363984 ] 

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

Simon this is where we're working on the IETF draft:

http://docs.safehaus.org/display/APACHEDS/LDAP+Extensions+for+Graceful+Shutdown

It will be implemented very soon in trunk.  Emmanuel has alread done all the ASN1 code.  I
can show you how to use an ExtendedRequest with JNDI to make this work.  It's really easy.
 However just bear with us as we try to get RC1 out the door.

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