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 "Simon Smith (JIRA)" <ji...@apache.org> on 2013/03/08 16:00:19 UTC

[jira] [Updated] (AXIS2-5498) ServiceDeployer.undeploy() fails to remove the entry from deploymentFileDataMap

     [ https://issues.apache.org/jira/browse/AXIS2-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Smith updated AXIS2-5498:
-------------------------------

    Attachment: AXIS2-5498.patch

Patch against 1.6.2.
                
> ServiceDeployer.undeploy() fails to remove the entry from deploymentFileDataMap
> -------------------------------------------------------------------------------
>
>                 Key: AXIS2-5498
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5498
>             Project: Axis2
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.6.2
>            Reporter: Simon Smith
>            Priority: Minor
>         Attachments: AXIS2-5498.patch
>
>
> In AbstractDeployer.deploy(), the DeploymentFileData instance is added to the Map using the absolute path of the service file (.aar). However ServiceDeployer.undeploy() passes the service name instead of the absolute path to super.undeploy() which means nothing is removed from the Map.
> The result is a leaked reference to the service's classloader, which cannot be garbage-collected (unless the service is redeployed, in which case the Map entry is replaced and the original classloader becomes eligible for collection).

--
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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org