activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2169) Web Console spawns new threads for every refresh and never kills any
Date Wed, 17 Jun 2009 14:58:35 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-2169.
-----------------------------

    Resolution: Fixed

scope of spring mvc beans was incorrect, should have been scope="request". Updated config
to match changed in activemq-web-console. The duplication (which is not good) is the result
of the broker config and properties files needing to be installation aware. Hense a distribution
needs a separate file.

> 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
>            Assignee: Gary Tully
>             Fix For: 5.3.0
>
>
> 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.


Mime
View raw message