[AMQ-3214] "InactivityMonitor Async Task" threads leaking

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 5.6.0
• Component/s: JMS client, Transport
• Assignee: Unassigned
• Reporter: Minh Do
• Created: 09/Mar/11 23:52
• Updated: 20/Sep/11 10:42
• Resolved: 29/Jun/11 23:42

Description

-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 continuously

This will cause the entire consumer system to slow down eventually due to thread context switching.

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 InactivityMonitor.java