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 "Kishore Guruswamy (JIRA)" <ji...@apache.org> on 2014/08/21 19:13:11 UTC
[jira] [Created] (AXIS2-5666) Large number of Timer threads
building up in Axis2 1.5 - Causing the Production Server to run out of
memory and shut down
Kishore Guruswamy created AXIS2-5666:
----------------------------------------
Summary: Large number of Timer threads building up in Axis2 1.5 - Causing the Production Server to run out of memory and shut down
Key: AXIS2-5666
URL: https://issues.apache.org/jira/browse/AXIS2-5666
Project: Axis2
Issue Type: Bug
Components: client-api
Affects Versions: 1.5
Environment: Websphere Application Server 6.1, Linux OS
Reporter: Kishore Guruswamy
Priority: Blocker
Hi
We are using Axis2 1.5 version to invoke web services.
We are seeing a large number of Timer threads (Timer-1, Timer-2...) build up, eventually causing the Production application server to run out of memory.
All of the timer threads are in wait condition
"Timer-110" Id=555 in WAITING on lock=java.util.TaskQueue@3e203e2
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:231)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:487)
To resolve the issue, We have leveraged the cleanUpTransport() method in the service client and also leveraged the Reuse Http Client option.
However, the issue still persists.
Looking for some insights on resolving the issue.
Thanks
Kishore G
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org