[
https://issues.apache.org/jira/browse/AXIS2-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490883
]
Michele Mazzucco commented on AXIS2-2328:
-----------------------------------------
Deepal,
where do you think the problem is?
I've looked at it some time ago, and I've found that there's only one object
(connection listener???) per configuration context. It would be much better to
use a separate connection listener for each ServiceClient. Does it make any
sense?
> 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, memory_allocation.jpg, 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]
