[
https://issues.apache.org/jira/browse/AXIS2-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168509#comment-14168509
]
Deepal Jayasinghe commented on AXIS2-5666:
------------------------------------------
What kind of invocation do you use ? async ?.
Deepal
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
