Affects Version/s: 5.2.0
Fix Version/s: 5.3.0
Red Hat x86_64, 2.6.9-55 kernel
Web console enabled (started in the same process as the broker)
How to reproduce:
- Use JMX to look at the threads.
- Open the web console gui and hit refresh.
For every refresh 1-2 new threads are spawned. These are never closed/killed and after a while the broker becomes unresponsive. (For us this happens after about 180-200 threads which corresponds to hitting refresh repeatedly for about one minute.)
The threads are named ActiveMQ Session ID:someId and is of type DedicatedTaskRunner.