[
https://issues.apache.org/jira/browse/AXIS2-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485149
]
Michele Mazzucco commented on AXIS2-2328:
-----------------------------------------
Dims,
I think the problem is quite serious. I've tried to change my client so that it
creates several ServiceClients object which send and wait for less messages,
but I was not able to fix the issue this way.
I think the root is described here
http://www.nabble.com/-Axis2--ServiceClient-question-tf2496516.html#a6959251
I'm using only 1 (multi threaded ) configuration context, so the memory is
released only at the end (or when I get an out of memory error :().
> Out of memory error in Callback receiver
> ----------------------------------------
>
> Key: AXIS2-2328
> URL: https://issues.apache.org/jira/browse/AXIS2-2328
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Affects Versions: nightly
> Environment: linux, sun jdk 1.5.0_10
> Reporter: Michele Mazzucco
> Priority: Critical
> Attachments: AXIS2-2328.patch, Picture 1.png
>
>
> The CallbackReceiver stores the callback object into a hash map, but it never
> removes it.
--
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]
