Hi Axis2-Team, While Tony reported this today for services only (AXIS2-633) it seems Axis2 does not have full lifecycle support.
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() ). Jens
