activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Minh Do (JIRA)" <>
Subject [jira] [Updated] (AMQ-3214) "InactivityMonitor Async Task" threads leaking
Date Thu, 19 May 2011 21:41:48 GMT


Minh Do updated AMQ-3214:

    Attachment: threadleak.png

This image is on the ActiveMQ client library after I ran using it stress test the ActiveMQ

> "InactivityMonitor Async Task" threads leaking
> ----------------------------------------------
>                 Key: AMQ-3214
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client, Transport
>            Reporter: Minh Do
>            Priority: Critical
>             Fix For: 5.6.0
>         Attachments: threadleak.png
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> -Have a multi-thread consumers running to consumer messages
> -Have Connection to have these :
>        		ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory(brokerUrl);
> 		connectionFactory.setUseAsyncSend(false);
> 		connectionFactory.setDispatchAsync(false);
> 		connectionFactory.setAlwaysSessionAsync(false);
> 		connectionFactory.setAlwaysSyncSend(true);
> -Run the consumers for several hours and profile it
> -You will see there are threads with the name "InactivityMonitor Async Task" being spawning
> This will cause the entire consumer system to slow down eventually due to thread context
> Suggestion to fix: we should not put a limit on the number of "InactivityMonitor Async
Task" threads to be Max Integer.  There is a bug in Java lib that
> it will not stop a thread after a given idle time-to-live. We could fix this in the file

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message