[ http://issues.apache.org/jira/brows...236419
9 ]

Simon Temple commented on DIREVE-330:
-------------------------------------

Thanks guys, I can see your very busy with RC1 right now...

I see the extension for graceful shutdown as very useful however when the di
rectory is embedded within an AS framework like JBoss (for example!) I feel 
it would be better to leave the shutting down of the directory to the AS fra
mework (via the controlled
un-deployment process).

In this way any dependencies between AS services can be controlled allowing 
a clean and graceful system shutdown.

Could we simply use an environment property to prohibit the installation of 
the shutdown handler and hence delegate the shutdown responsibility to the a
pplication server framework?

SimonT


> 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 shutdow
n
> 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/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]