[jira] Commented: (AXIS2-640) Axis2 Lifecycle

["Davanum Srinivas (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/AXIS2-640?page=comments#action_12377075 ] 

Davanum Srinivas commented on AXIS2-640:
----------------------------------------

moved the closeAllConnectors to the cleanup(msgContext) method inside JMSSender and got rid of the addShutdownHook.

> Axis2 Lifecycle
> ---------------
>
>          Key: AXIS2-640
>          URL: http://issues.apache.org/jira/browse/AXIS2-640
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>     Reporter: Davanum Srinivas

>
> Quote from Jens Schumann : Discussion @ http://marc.theaimsgroup.com/?t=114626733700001&r=1&w=2
> Since I was trying to come up with a fix for Axis2-595 I was looking for
> something within Axis2 codebase which would help to do some cleanup during
> shutdown. It turned out that the Axis2 deployment engine is not exposed for
> clean shutdown and Handler#cleanup()/ TransportSender#cleanUp(MessageContext
> msgContext) is never called.
> Before spending too many cycles in refactoring could someone from the axis2
> team comment on the current plans for full lifecycle support, especially
> shutdown which can be called externally.
> Specifically I would like to
> - Shutdown the deployment engine and with it the scheduler,
> - Ensure to call all cleanup() methods,
> - Release all Classloader references during shutdown,
> - Remove the ShutdownHook from JMSSender and move it to a global
> ShutdownHook which is used for standalone axis2 mode only (the sender should
> deregister from JMS within cleanup() ).

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