[
https://issues.apache.org/jira/browse/AMQ-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205810#comment-13205810
]
Timothy Bish commented on AMQ-3710:
-----------------------------------
First suggestion is to upgrade to the latest Apache release v5.5.1 or try a
SNAPSHOT build of 5.6 as there have been numerous bug fixes. Otherwise we'd
need more to go on like your broker configuration and logs from the broker with
debug tracing on.
> Activemq broker hangs
> ---------------------
>
> Key: AMQ-3710
> URL: https://issues.apache.org/jira/browse/AMQ-3710
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Environment: cent os linux version 5, 64 bit os, java 1.6 update 21
> Reporter: Krishnadasan T S
> Priority: Blocker
>
> I am using activeMQ 5.4.2 as separate process in my production. more than
> 2000 topics and 600 clients are connecting to broker. Heap size (Old
> generation) area is taking nearly 1 gb memory. Total memory allocated to jvm
> is 2.5 gb.
> Activemq is getting hanged 2 or 3 time in a day. by monitoring in JMX
> console What we noticed is that at that instance of time nearly 100 new
> threads are created and all these threads are NIO related threads. Once It
> happened at the time of GC(we gave a perform gc from jmx for testing). It
> also happened at normal time also.
> can you give any suggestion about what can be the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
