[
http://jira.jboss.com/jira/browse/JBESB-438?page=comments#action_12359665 ]
Kevin Conner commented on JBESB-438:
------------------------------------
Mark, can you elaborate on this please?
With the current codebase anything within a single .esb file should already be taken down
cleanly.
The order used to specify the listeners/gateways is the sequence used by the managed
lifecycle controller to initialise/start the lifecycles. When the managed lifecycle
stops/destroys the lifecycles then the order is reversed.
Each listener/gateway should wait until current work has finished before being destroyed,
subject to timeout.
Now that there is a move to deploy multiple .esb files we must make sure that the
dependencies *between* those .esb files are fully realised. I do not believe the current
codebase is in a position to do this and would have been happier if this had been deferred
until 5 where we will have proper MC/OSGi integration.
Controlled shutdown
-------------------
Key: JBESB-438
URL:
http://jira.jboss.com/jira/browse/JBESB-438
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.0
Reporter: Mark Little
Assigned To: Kevin Conner
Fix For: 4.2 Milestone Release 2, 5.0 Milestone Release 1
During a controlled shutdown, the ESB should prevent any further message inflow but allow
all messages being processed/delivered to finish.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira