[ http://issues.apache.org/jira/brows...236420
4 ]

Emmanuel Lecharny commented on DIREVE-330:
------------------------------------------

Ok, I get your point.

What you need, is a shutdown service that allows two things :
- Stop accepting new requests, but achieves the current requests
- Allow a kind of ShutDown user to send some last requests to ADS if needed,
 just before shutdowning the server smoothly (for instance, it could be "cle
an this specific context...")

Don't forget that ADS? at this point, is not transactionnal. Operations cann
ot be encapsulated into database like transaction, with a commit and rollbac
k (this is a cool feature we need, however). So your users won't be aware if
 the server just shutdown.
This could be a problem if you want the users to be able to rollback themsel
f their actions before the server shutown. Also consider that if the server 
just crash, you are exactly in the same situation ;)

At least, the GracefulShutdown command is much better than any other slution
, in that way it works smoothly, and can also be extended in a way that allo
ws users to obtain the result of a time consuming request before the shutdow
n.

Their are many path to explore, many improvment to develop. But this is pret
ty much something to put in the 1.1, 1.2 or 2.0 roadmap.

I don't know if this answer is acceptable regarding your timeframe, may be A
lex has a different point of view. However, this is really interesting to go
 farther in your direction, I think.

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