You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Ciaran Jessup (JIRA)" <ji...@apache.org> on 2009/04/14 18:42:14 UTC
[jira] Created: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
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
When un-deploying a DeploymentUnitDir object instance is kept in memory, this is a direct consequence of this Axis bug ( ) 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.
[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ciaran Jessup updated ODE-580:
------------------------------
Description:
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 :)
was:
When un-deploying a DeploymentUnitDir object instance is kept in memory, this is a direct consequence of this Axis bug ( ) 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 :)
> 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.
[jira] Commented: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700344#action_12700344 ]
Alexis Midon commented on ODE-580:
----------------------------------
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
> 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.
[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ciaran Jessup updated ODE-580:
------------------------------
Attachment: FixForAxisBug.patch
This patch uses reflection to properly clear down the endpoints hashmap when a service is removed.
> 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 ( ) 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.
[jira] Resolved: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon resolved ODE-580.
------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1
fixed in 1.X, r766175
Zillions thanks to Ciaran for the patch.
> 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: 1.3.1, 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.
[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "Ciaran Jessup (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ciaran Jessup updated ODE-580:
------------------------------
Priority: Minor (was: Major)
> 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
>
> When un-deploying a DeploymentUnitDir object instance is kept in memory, this is a direct consequence of this Axis bug ( ) 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.
[jira] Commented: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "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.
[jira] Issue Comment Edited: (ODE-580) DeploymentUnitDir object
gets leaked after un-deployment.
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-580) DeploymentUnitDir object gets leaked
after un-deployment.
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-580:
-----------------------------
Affects Version/s: 2.0
1.3.1
Fix Version/s: 2.0
Assignee: Alexis Midon
> 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.