[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
