activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@activemq.org>
Subject [jira] Resolved: (AMQ-407) Thread leak when cluster node disappears
Date Fri, 17 Mar 2006 14:25:26 GMT
     [ http://jira.activemq.org/jira//browse/AMQ-407?page=all ]
     
james strachan resolved AMQ-407:
--------------------------------

     Resolution: Fixed
    Fix Version: 4.0 M5

Should now be fixed in 4.0-M5

> Thread leak when cluster node disappears
> ----------------------------------------
>
>          Key: AMQ-407
>          URL: http://jira.activemq.org/jira//browse/AMQ-407
>      Project: ActiveMQ
>         Type: Bug

>   Components: Transport, Broker
>     Versions: 3.1, 3.2
>  Environment: JDK 1.5.0_04, RedHat ES 3, Resin 3.0.14, Spring 1.2.5
>     Reporter: Christopher G. Stach II
>      Fix For: 4.0 M5
>  Attachments: activemq.xml, threadleak.txt
>
>
> In a network of three brokers, if one disappears, the other two brokers' JVMs eventually
run out of memory due to the leaked threads.  This is not alleviated if the dropped broker
reappears in the network.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message