[
https://issues.apache.org/jira/browse/AXIS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS-524.
----------------------------------
Resolution: Won't Fix
Won't fix:
* Re/undeploying a service while there are active sessions is a very rare use
case that probably 99% of all users never encounter.
* The (partial) fix for this issue caused a memory leak (AXIS-2314), the fix
for which in turn caused a thread safety issue (AXIS-2878).
* One may argue that if a service is redeployed, then existing sessions should
actually be served by the old service object. Otherwise the session state will
be lost. If one follows that argument, then there is no issue.
> Re/Undeploying doesn't clear session cache
> ------------------------------------------
>
> Key: AXIS-524
> URL: https://issues.apache.org/jira/browse/AXIS-524
> Project: Axis
> Issue Type: Bug
> Components: Deployment / Registries
> Environment: Operating System: Other
> Platform: All
> Reporter: Dug
> Assignee: James Snell
>
> When a service is undeployed or redeployed it needs to be
> removed from the session caches so that a new service object
> will be created the next time its invoked.
> Axis needs to remove the service object from the 2 sessions
> in the Engine (the "session" one as well as the "application" one).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
