[ 
https://issues.apache.org/jira/browse/AMQ-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206792#comment-13206792
 ] 

Krishnadasan T S commented on AMQ-3710:
---------------------------------------

Hi,

Today  I checked the status of kahadb files. It contains a db-794.log file 
having 32 mb, db.redo file having 1.1 mb and db.data having a big 5 GB.

Why is this db.store file having such a huge size. is there any chance to have 
this to cause the above issue. if it is so can i expect it to solved in 5.5.1 
version.

Another thing is about db-794.log file. As per Normally log rotation, the 
latest file will be a non numbered file. But in this case i can only see 
db-794.log. If it is logging only non consumed messages then it seems ok.

Any way we are planning to upgrade activemq vesion to 5.5.1 in production.



  
                
> 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

        

Reply via email to