You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2008/06/24 11:12:45 UTC

[jira] Updated: (AXIS2-3870) Memory Leak using ServiceClient

     [ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans G Knudsen updated AXIS2-3870:
----------------------------------

    Attachment: ClientLeak.java

The attached testclient uses the Axis2 1.4 sample :

samples/src/userguide/clients/EchoBlockingWsaBasedClient.java

as basis - modified with global initialization of ConfigurationContext + a loop...

The corresponding service is also from Axis2 1.4 samples :

WsaMappingService.aar


Running the client in Eclipse with 64M for the session - the client gives up after about 800 invocations... 


> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org