Affects Version/s: 1.5
Fix Version/s: None
Environment:Websphere Application Server 6.1, Linux OS
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)
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.