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:02:45 UTC
[jira] Created: (AXIS2-3870) Memory Leak using ServiceClient
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
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
Re: [jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by keith chapman <ke...@gmail.com>.
Can you try this on the nightly build please. There was a memory leak that
was fixed on the trunk and it was post 1.4.1.
Thanks,
Keith.
On Sat, Dec 6, 2008 at 12:42 AM, Satyanarayana Murthy Godavarti (JIRA) <
jira@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653895#action_12653895]
>
> Satyanarayana Murthy Godavarti commented on AXIS2-3870:
> -------------------------------------------------------
>
> Hi Amila,
>
> I tested my code with latest Axis2 1.4.1 version. I did not see any
> improvement in the memory leaks. Application is consuming huge amount of
> memory and getting terminated after few iterations. Can you please advise
>
>
>
>
>
> > 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
> > Fix For: 1.4.1
> >
> > 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
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608298#action_12608298 ]
Amila Chinthaka Suriarachchi commented on AXIS2-3870:
-----------------------------------------------------
Please see the removeServiceGroup method.
which removes all the services of the service group.
public AxisServiceGroup removeServiceGroup(String serviceGroupName) throws AxisFault {
AxisServiceGroup axisServiceGroup = (AxisServiceGroup) getChild(serviceGroupName);
if (axisServiceGroup == null) {
throw new AxisFault(Messages.getMessage("invalidservicegroupname",
serviceGroupName));
}
Iterator services = axisServiceGroup.getServices();
while (services.hasNext()) {
AxisService axisService = (AxisService) services.next();
allServices.remove(axisService.getName());
if (!axisService.isClientSide()) {
notifyObservers(AxisEvent.SERVICE_REMOVE, axisService);
}
}
removeChild(serviceGroupName);
notifyObservers(AxisEvent.SERVICE_REMOVE, axisServiceGroup);
return axisServiceGroup;
}
I tested with this client.
ConfigurationContext configurationContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(
AXIS2_REPOSITORY_LOCATION, AXIS2_CLIENT_CONFIG_FILE);
ServiceClient serviceClient = new ServiceClient(configurationContext, null);
serviceClient.setTargetEPR(new EndpointReference("http://localhost:8088/axis2/services/PlainTestInOutService"));
serviceClient.getOptions().setAction("urn:PlainTestInOutOperation");
OMElement response = serviceClient.sendReceive(getTestOMElement("test"));
System.out.println("OMElement ==> " + response.toString());
serviceClient.cleanup();
try {
System.out.println("Waiting thread to sleep");
Thread.sleep(2000);
} catch (InterruptedException e) {
here I put a debug point at serviceClient.cleanup() method and checked. before this statement there was a service and after that it has removed.
> 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
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608150#action_12608150 ]
Hans G Knudsen commented on AXIS2-3870:
---------------------------------------
Hi!
The Obects which does not seem to get freed are :
org.apache.axis2.descrition.AxisServiceGroup
org.apache.axis2.descrition.AxisService
org.apache.axis2.descrition.OutOnlyAxisOperation
org.apache.axis2.descrition.RobustOutOnlyAxisOperation
org.apache.axis2.descrition.OutOnlyAxisOperation
org.apache.axis2.engine.DefaultObjectSupplier
The
ServiceClient.cleanup()
do call :
axisConfiguration.removeServiceGroup(serviceGroupName);
but this does not seam to be sufficient.
/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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Satyanarayana Murthy Godavarti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653895#action_12653895 ]
Satyanarayana Murthy Godavarti commented on AXIS2-3870:
-------------------------------------------------------
Hi Amila,
I tested my code with latest Axis2 1.4.1 version. I did not see any improvement in the memory leaks. Application is consuming huge amount of memory and getting terminated after few iterations. Can you please advise
> 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
> Fix For: 1.4.1
>
> 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
[jira] Updated: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
[ 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
Re: [jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by Martin <mg...@hotmail.com>.
Hans-
did you have the chance to try alternate JVM heap startup params via
$JAVA_OPTS...e.g.?
//to specify alternate stack
-XssStackSize
//initial Java Memory heap
-Xms256m
//to specify max heap
-Xmx512m
//to specify PermGen
-XX:MaxPermSize=512m -XX:+PrintGCDetails -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled
(restart TC or container using $JAVA_OPTS)
?
Martin
----- Original Message -----
From: "Hans G Knudsen (JIRA)" <ji...@apache.org>
To: <ax...@ws.apache.org>
Sent: Tuesday, June 24, 2008 8:22 AM
Subject: [jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
>
> [
> https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607593#action_12607593 ]
>
> Hans G Knudsen commented on AXIS2-3870:
> ---------------------------------------
>
> Hi Michele!
>
> By 'give up' I meant : runs out of memeory :
>
> Invoke ClientLeak : 808
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.<init>(HashMap.java:203)
> at
> org.apache.axis2.description.PolicySubject.<init>(PolicySubject.java:36)
> at
> org.apache.axis2.description.AxisDescription.<init>(AxisDescription.java:79)
> at
> org.apache.axis2.description.AxisBindingMessage.<init>(AxisBindingMessage.java:88)
> at
> org.apache.axis2.deployment.util.Utils.populateBindingOperation(Utils.java:1477)
> at
> org.apache.axis2.deployment.util.Utils.populateSoap11Endpoint(Utils.java:1354)
> at
> org.apache.axis2.deployment.util.Utils.addEndpointsToService(Utils.java:1157)
> at
> org.apache.axis2.engine.AxisConfiguration.processEndpoints(AxisConfiguration.java:1234)
> at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:329)
> at
> org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:293)
> at
> org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:175)
> at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:143)
> at dk.gov.oiosi.test.client.ClientLeak.run(ClientLeak.java:49)
> at dk.gov.oiosi.test.client.ClientLeak.main(ClientLeak.java:120)
>
>
> /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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607593#action_12607593 ]
Hans G Knudsen commented on AXIS2-3870:
---------------------------------------
Hi Michele!
By 'give up' I meant : runs out of memeory :
Invoke ClientLeak : 808
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.<init>(HashMap.java:203)
at org.apache.axis2.description.PolicySubject.<init>(PolicySubject.java:36)
at org.apache.axis2.description.AxisDescription.<init>(AxisDescription.java:79)
at org.apache.axis2.description.AxisBindingMessage.<init>(AxisBindingMessage.java:88)
at org.apache.axis2.deployment.util.Utils.populateBindingOperation(Utils.java:1477)
at org.apache.axis2.deployment.util.Utils.populateSoap11Endpoint(Utils.java:1354)
at org.apache.axis2.deployment.util.Utils.addEndpointsToService(Utils.java:1157)
at org.apache.axis2.engine.AxisConfiguration.processEndpoints(AxisConfiguration.java:1234)
at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:329)
at org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:293)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:175)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:143)
at dk.gov.oiosi.test.client.ClientLeak.run(ClientLeak.java:49)
at dk.gov.oiosi.test.client.ClientLeak.main(ClientLeak.java:120)
/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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Satyanarayana Murthy Godavarti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657037#action_12657037 ]
Satyanarayana Murthy Godavarti commented on AXIS2-3870:
-------------------------------------------------------
HI,
I found memory leaks are reduced with the nightly build. I am getting ClassNotDefFound error while invoking the web service end point. The exception occured is Caused by: java.lang.ClassNotFoundException: org.apache.axis2.transport.tcp.TCPTransportSender. I set axis2-kernel-SNAPSHOT.jar in my application classpath. I am providing full print stack trace here. please advice
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:679)
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:124)
at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:707)
at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:206)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:146)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:139)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:245)
at com.siemens.energy.soa.scf.wscommunication.httpinvoker.AxisHTTPClient.sendHTTP(AxisHTTPClient.java:190)
at com.siemens.energy.soa.scf.wscommunication.WSCommunicationImpl.invokeWSEndpoint(WSCommunicationImpl.java:77)
at com.siemens.energy.soa.dispatcher.Dispatcher.dispatch(Dispatcher.java:85)
at com.siemens.energy.soa.scf.serverside.Worker.run(Worker.java:95)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.apache.axis2.transport.tcp.TCPTransportSender
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:654)
... 15 more
> 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
> Fix For: 1.4.1
>
> 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.
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Satyanarayana Murthy Godavarti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655267#action_12655267 ]
Satyanarayana Murthy Godavarti commented on AXIS2-3870:
-------------------------------------------------------
Hi,
I have downloaded AXIS2-NIGHTLY-226 from http://builder.wso2.org/browse/AXIS2-NIGHTLY-224/artifact link. I found few jar files in Lib folder with SNAPSHOT at the end of each jar file. Example axis2-kernel-SNAPSHOT.jar, axis2-adb-SNAPSHOT.jar etc. The size of these jar files are not same as Axis2 version 1.4.1 and the size is smaller. I have tested my code with Axis2 nightly build jars and I got ClassNotDefFound errors. Can you guys please help us on how to test the code using nightly build jar files. This is very urgent. Our application is getting terminated due to memory leaks in ServiceClient object. We are tracking this issue AXIS2-3870.
Thanks
Regards,
Satya
> 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
> Fix For: 1.4.1
>
> 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.
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-3870.
-------------------------------------------------
Resolution: Fixed
fixed the issue with revision 672607.
in AxisConfiguration the allEndPoints map has not been cleared.
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisConfiguration.java?r1=660986&r2=672607
> 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
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655526#action_12655526 ]
Amila Chinthaka Suriarachchi commented on AXIS2-3870:
-----------------------------------------------------
What is the class which causes ClassNotDefFound?
> 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
> Fix For: 1.4.1
>
> 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.
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613916#action_12613916 ]
Amila Chinthaka Suriarachchi commented on AXIS2-3870:
-----------------------------------------------------
Applied to branch
> 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
> Fix For: 1.4.1
>
> 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
[jira] Commented: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608138#action_12608138 ]
Hans G Knudsen commented on AXIS2-3870:
---------------------------------------
Hi!
I just tested the same client with Axis2 1.3.
Here I donot see the Memory leak.
/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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya updated AXIS2-3870:
----------------------------------------------
Fix Version/s: 1.4.1
> 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
> Fix For: 1.4.1
>
> 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
[jira] Updated: (AXIS2-3870) Memory Leak using ServiceClient
Posted by "Serge Sozonoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Serge Sozonoff updated AXIS2-3870:
----------------------------------
Attachment: 2.jpg
1.jpg
I would like to re-open this bug report. We are running 1.4.1 and continue to see a memory leak.
Please see attachments. Allocated heap size keeps increasing, allocation graph can be seen in 2.jpg
Serge
> 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
> Fix For: 1.4.1
>
> Attachments: 1.jpg, 2.jpg, 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.