You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2009/04/17 23:58:14 UTC
[jira] Issue Comment Edited: (ODE-580) DeploymentUnitDir object
gets leaked after un-deployment.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700344#action_12700344 ]
Alexis Midon edited comment on ODE-580 at 4/17/09 2:56 PM:
-----------------------------------------------------------
I created AXIS2-4314 to track this issue.
Trunk has a workaround (because it uses Axis2 1.4.1), see r766164. http://svn.apache.org/viewvc?view=rev&revision=766164
was (Author: alexismidon):
I created AXIS2-4314 to track this issue.
Trunk has workaround, see r766164. http://svn.apache.org/viewvc?view=rev&revision=766164
> DeploymentUnitDir object gets leaked after un-deployment.
> ---------------------------------------------------------
>
> Key: ODE-580
> URL: https://issues.apache.org/jira/browse/ODE-580
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.3.1, 2.0
> Environment: na
> Reporter: Ciaran Jessup
> Assignee: Alexis Midon
> Priority: Minor
> Fix For: 2.0
>
> 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.