[ http://issues.apache.org/jira/browse/DIREVE-330?page=all ]
     
Alex Karasulu resolved DIREVE-330:
----------------------------------

    Fix Version: 0.9.4
     Resolution: Fixed

Committed revision 373292.

Now you can add the following to your configuration:

  <bean id="configuration" 
class="org.apache.ldap.server.configuration.MutableServerStartupConfiguration">
    <property name="shutdownHookEnabled"><value>false</value></property>
...

This will prevent the shutdown hook from being registered.  When starting 
programatically in embedded configurations just call 
setShutdownHookEnabled(false) on the MutableStartupConfiguration or the 
MutableServerStartupConfiguratioin.

> 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
>      Fix For: 0.9.4

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

Reply via email to