axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hans G Knudsen (JIRA)" <>
Subject [jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Date Thu, 26 Jun 2008 12:15:45 GMT


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


> Memory Leak using ServiceClient
> -------------------------------
>                 Key: AXIS2-3870
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.4
>            Reporter: Hans G Knudsen
>         Attachments:
> 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:
For additional commands, e-mail:

View raw message