[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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Incomplete
• Affects Version/s: 1.5
• Component/s: client-api
• Environment: Websphere Application Server 6.1, Linux OS
• Assignee: Unassigned
• Reporter: Kishore Guruswamy
• Created: 21/Aug/14 17:13
• Updated: 16/Apr/16 20:41
• Resolved: 16/Apr/16 20:41

Description

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