directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIREVE-330) Allow the installation of the shutdown handler to be optional for embedded servers
Date Fri, 27 Jan 2006 11:01:40 GMT
    [ ] 

Emmanuel Lecharny commented on DIREVE-330:

Hi Simon,

the problem with shutdown is that we need to clean the network layer (correctly free sockets
mainly). As you certainly already experienced, depending on your system configuration, when
you jsut "kill" the jvm running ADS, you will be locked because the port will still be in
use. To avoid such a behavior, we need to be able to ask the server to commit suicide. This
is the GracefulShutdown command.

This handler is *not* mandatory. If you don(t call it, then you will have to kill the process
and wait a few seconds before being able to launch the server again on the same port. So there
is no need for a property parameter to prohibit this handmer to be called.

In your case, there is something different that should be done. We have to investigate the
way AS are stopping or un-deploying applications. I don't know if JBoss support JSR88 or has
a undeployment feature that allow the developper to execute a specific action like calling
GracefulShutdown, but, in my mind, this is the way to go.

I hope it helps... Any other idea on the subject are welcome !

> Allow the installation of the shutdown handler to be optional for embedded servers
> ----------------------------------------------------------------------------------
>          Key: DIREVE-330
>          URL:
>      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:
For more information on JIRA, see:

View raw message