[ 
https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672585#action_12672585
 ] 

Matthew Brown commented on AXIS-2668:
-------------------------------------

We have a similar problem. We don't use SOAP attachments so it looks to me like 
modifying Axis by removing org.apache.axis.MessageContext#finalize would 
resolve the poor memory usage profile.

I haven't had an opportunity to test this yet. Any thoughts?

> Axis 1.3 - Garbage collection issue
> -----------------------------------
>
>                 Key: AXIS-2668
>                 URL: https://issues.apache.org/jira/browse/AXIS-2668
>             Project: Axis
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: OS - AIX Application Server Oracle Applicatio Server, 
> AXIS Version 1.3
>            Reporter: Prasanna Sundarrajan
>            Priority: Critical
>         Attachments: com.zip
>
>
> Hi All, 
> This is Prasanna. Currently I am working for an application which is a 
> service oriented application. 
> The services are designed using Java - Axis 1.3 and the services are hosted 
> by the Oracle Application 
> Server running under AIX (IBM JDK version 1.5) and the services are consumed 
> by .net application. 
> During our performance load testing we found a weird behavior in our 
> application. We would like to share the same with you. It would be great if 
> any of you kindly look in to the below issue and give any solution to resolve 
> the same. 
> We had encountered Out-of memory exception in 
> the java application server when a single user performs the same transaction 
> repeatedly for more than 30 minutes. We tested this scenario using 
> performance 
> load scripts. We have analyzed the heap dump and found that the objects 
> created in the application server are not garbage collected and they still 
> have references and all the references are created under MessageContext 
> objects. 
> As part of this exercise we profiled the java code and none of the code has 
> memory leaks. 
> We would like to know how this to be handled do we need to close or dispose 
> anything explicitly. Looking forward your valuable response. Any help or 
> pointer is highly appreciated.
> Thanks in advance
> Prasanna. 

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

Reply via email to