[
https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608399#action_12608399
]
Hans G Knudsen commented on AXIS2-3870:
---------------------------------------
Hi Amila!
The AxisServiceGroup does get freed...
But the above mentioned objects do not...
With the ClientLeak giving up trying to send message no 808 - I have 807 of
each - according to my profiler....
These were the obvious leaking objects - but there might be a few more...
I tried to follow the allocations trying to find where they were referred
(hashmaps/hashtables/arraylists) in the internal Axis structures - but have not
yet found the place which keeps holding the reference.
/hans
> Memory Leak using ServiceClient
> -------------------------------
>
> Key: AXIS2-3870
> URL: https://issues.apache.org/jira/browse/AXIS2-3870
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Reporter: Hans G Knudsen
> Attachments: ClientLeak.java
>
>
> Hi!
> I think I see a leak when using ServiceClient.
> In my client I intialize the ConfigurationContext once and resuse it to
> initialize the ServiceClient :
> ServiceClient sender = new ServiceClient(configContext,null);
> Calling 'cleanup()' on the ServiceClinet explicitly after the service call
> does not help..
> I will supply a small testcase.
> /hans
--
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]
