[jira] Commented: (ODE-580) DeploymentUnitDir object gets leaked after un-deployment.

["Alexis Midon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700296#action_12700296 ] 

Alexis Midon commented on ODE-580:
----------------------------------

I checked the latest Axis2 code [1], and I don't think the issue is completely fixed. Actually when removeService() is invoked, the endpoint map is not cleaned up. They clean it up only when you call removeServiceGroup.

So I'll get back to the axis2 guys, take a look at your patch for 1.X, see if we could use removeServiceGroup to workaround for trunk.

[1] http://jukka.zitting.name/git/?p=axis2-java.git;a=blob;f=modules/kernel/src/org/apache/axis2/engine/AxisConfiguration.java;h=9002f1372ad50afa3659423b5c5bf701fb4406ab;hb=1_5#l606

> DeploymentUnitDir object gets leaked after un-deployment.
> ---------------------------------------------------------
>
>                 Key: ODE-580
>                 URL: https://issues.apache.org/jira/browse/ODE-580
>             Project: ODE
>          Issue Type: Bug
>         Environment: na
>            Reporter: Ciaran Jessup
>            Priority: Minor
>         Attachments: FixForAxisBug.patch
>
>
> When un-deploying a DeploymentUnitDir object instance is kept in memory,  this is a direct consequence of this Axis bug ( http://issues.apache.org/jira/browse/AXIS2-3870 ) which has been resolved in Axis2 1.4 (I know there's an ODE fork running that version out there...)  
> There follows a *HORRIBLE* 'fix' to this issue that resolves the memory leak, but I would suggest a move to a later revision of Axis rather than this particular patch :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.