[
https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS-2668.
-----------------------------------
Resolution: Incomplete
Resolving this issue as incomplete. Reason: it has been claimed that the memory
is held by MessageContext objects awaiting finalization. However, this doesn't
necessarily mean that the issue is caused by Axis (in particular considering
the fact that the finalize method in MessageContext normally completes very
quickly). There are at least two other possible explanations:
* There is other code unrelated to Axis running in the same JVM that also makes
use of finalization and that has finalize methods that take too much time to
complete, causing objects to pile up in the finalizer queue.
* There is an issue in the JVM that causes it to trigger an OOM error without
giving enough time to the finalizer thread.
Unfortunately, there is not enough information in the issue report to determine
the root cause, and 5 years after the last update by the reporter it will be
difficult to collect that information.
> 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
> Labels: memory-leak
> 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.
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: [email protected]
For additional commands, e-mail: [email protected]
