You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2006/04/29 12:45:38 UTC
[jira] Created: (AXIS2-640) Axis2 Lifecycle
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
[jira] Commented: (AXIS2-640) Axis2 Lifecycle
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-640?page=comments#action_12377091 ]
Davanum Srinivas commented on AXIS2-640:
----------------------------------------
We've cleaned up the JMSSender and here's the quote from deepal on the other work in this area:
http://marc.theaimsgroup.com/?l=axis-dev&m=114628751716109&w=2
"This method will be called when the session get expired , but I just
found a bug in the code that when you deploy a service in application
scope then its destroy method is not calling. I fixed that , if some one
called ListernManer.stop() at that point destroy method of all the
available serviceCotetxt will be called. I modified AxisServelet as well."
> 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
> Assignee: Deepal Jayasinghe
>
> 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
[jira] Commented: (AXIS2-640) Axis2 Lifecycle
Posted by "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
[jira] Resolved: (AXIS2-640) Axis2 Lifecycle
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-640?page=all ]
Deepal Jayasinghe resolved AXIS2-640:
-------------------------------------
Resolution: Fixed
> 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
> Assignee: Deepal Jayasinghe
>
> 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
[jira] Assigned: (AXIS2-640) Axis2 Lifecycle
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-640?page=all ]
Davanum Srinivas reassigned AXIS2-640:
--------------------------------------
Assign To: Deepal Jayasinghe
Deepal,
Did you add code to stop the scheduler as well in AxisServlet?
thanks,
dims
> 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
> Assignee: Deepal Jayasinghe
>
> 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