You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Prasanna Sundarrajan (JIRA)" <ax...@ws.apache.org> on 2007/05/28 10:07:15 UTC
[jira] Created: (AXIS-2668) Axis 1.3 - Garbage collection issue
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
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Bjorn Townsend (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511816 ]
Bjorn Townsend commented on AXIS-2668:
--------------------------------------
Prasanna -- I'm happy to look into this, but as I'm not part of Axis my time is pretty limited. I probably won't be able to get to it for several weeks.
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Tom Jordahl (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507898 ]
Tom Jordahl commented on AXIS-2668:
-----------------------------------
Hi Prasanna,
I am afraid you get what you pay for in Open Source Land and if you have a problem with Axis 1.4, then you are probably going to have to do the needful yourself. Most of the active Axis developers are working on Axis2 (the next generation) and Axis 1.4 is in benign neglect mode.
We would love you have you post a patch here against the current SVN source if you do find a problem with the current Axis 1.x source tree.
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Bjorn Townsend (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499683 ]
Bjorn Townsend commented on AXIS-2668:
--------------------------------------
Prasanna,
Have you tried to reproduce this issue with the latest version of Axis (1.4)? There were a number of memory leak issues resolved in that version. Failing that, in order to diagnose the cause of the garbage collection issue I'd need to see code that reproduced the issue, unless you can be more specific.
Bjorn
> 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
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Matthew Brown (JIRA)" <ax...@ws.apache.org>.
[ 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.
[jira] Updated: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Prasanna Sundarrajan (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasanna Sundarrajan updated AXIS-2668:
---------------------------------------
Attachment: com.zip
Hi Bjorn,
I have attached the sample application module code for your reference. The attached code will be called by the SecurityService class ( normal method invocation) and it will go via the EJB layer.
Using Java2WSDL we will generate the WSDL and update the ServerConfig.wsdd according to the WDSL defintiion, the same will be packed as a ear with axis jars and deployed into the server.
Kindly look into the code and let us know if you need any further information/inputs on this issue.
As i mentioned earlier our production install is on hold because of this issue, so kindly help us out on this. Any links/pointers also would be highly appreciated.
Waiting to hear from you.
Thanks and Regards
Prasanna
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Prasanna Sundarrajan (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501091 ]
Prasanna Sundarrajan commented on AXIS-2668:
--------------------------------------------
Hi All,
Can one you update me on this issue, this is very critical for us. Kindly look into this and do the needful.
Thanks and Regards
Prasanna
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue
Posted by "Prasanna Sundarrajan (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499805 ]
Prasanna Sundarrajan commented on AXIS-2668:
--------------------------------------------
Hi Bjorn,
Yes, we tried with Axis 1.4 also, there also the behaviour is consistent.
As per our application requirement the volume of data involved is large(around 3 to 4 MB) in few transaction and we found that all these objects are being held by org/apache/axis/MessageContext objects. These MessageContext objects are inturn being held by java/lang/ref/Finalizer objects.
So we are not sure whether the finalizers are executed and hence the MessageContext objects will not be removed from the heap. (MessageContext.finalize() method)
If the user performing the same transaction(transaction involves 4MB of data) for around 30 minutes then we are getting outofmemory issue. Is there any other alternative to this problem, can we force the finalizer by running "System.runFinalization" externally? Any idea or any other pointers? Kindly let me know.
Thanks and Regards
Prasanna
> 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
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org