[
https://issues.apache.org/activemq/browse/AMQ-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51917#action_51917
]
Benjamin Darfler commented on AMQ-2169:
---------------------------------------
I would love to get some movement on this! I was using the web console to fix
https://issues.apache.org/activemq/browse/AMQ-1112
> Web Console spawns new threads for every refresh and never kills any
> --------------------------------------------------------------------
>
> Key: AMQ-2169
> URL: https://issues.apache.org/activemq/browse/AMQ-2169
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Environment: Red Hat x86_64, 2.6.9-55 kernel
> Web console enabled (started in the same process as the broker)
> Reporter: Erik Drolshammer
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
