You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by joechen8310 <jo...@ericsson.com> on 2015/12/28 11:49:55 UTC
Using the pure java LevelDB implementation but saw kahadb in thread
dump file
I am sure i have configured to using levelDB in activemq.xml, and the console
also tell me I am using the LevelDB implementation, but i only saw kahadb in
the thread dump file as below. I am not sure whether this cause the broker
performance , but the performance of queue is very poor, it is only a fews
thousands with 40 consumers in one queue, and we only have one queue. can
somebody help ?
Thanks very much
"JobScheduler:JMS" daemon prio=10 tid=0x00007fa8dd3ba000 nid=0x339a in
Object.wait() [0x00007fa85f507000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at
org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl$ScheduleTime.pause(JobSchedulerImpl.java:895)
- locked <0x000000056ed67ec0> (a java.lang.Object)
at
org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.mainLoop(JobSchedulerImpl.java:775)
at
org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.run(JobSchedulerImpl.java:673)
at java.lang.Thread.run(Thread.java:745)
"ActiveMQ Broker[10.175.190.171] Scheduler" daemon prio=10
tid=0x00007fa8dd39e000 nid=0x3399 in Object.wait() [0x00007fa85f548000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:552)
- locked <0x000000056eda71b8> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:505)
"ActiveMQ Data File Writer" daemon prio=10 tid=0x00007fa8dd39f800 nid=0x3398
in Object.wait() [0x00007fa85f589000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x000000056ed6bdf0> (a java.lang.Object)
at java.lang.Object.wait(Object.java:503)
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAppender.processQueue(DataFileAppender.java:306)
- locked <0x000000056ed6bdf0> (a java.lang.Object)
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAppender$1.run(DataFileAppender.java:193)
"ActiveMQ Journal Checkpoint Worker" daemon prio=10 tid=0x00007fa8dd398000
nid=0x3397 waiting on condition [0x00007fa85f5ca000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at
org.apache.activemq.store.kahadb.AbstractKahaDBStore$2.run(AbstractKahaDBStore.java:691)
"KahaDB Scheduler" daemon prio=10 tid=0x00007fa8dd38d800 nid=0x3396 in
Object.wait() [0x00007fa85f60b000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:552)
- locked <0x000000056ed69958> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:505)
--
View this message in context: http://activemq.2283324.n4.nabble.com/Using-the-pure-java-LevelDB-implementation-but-saw-kahadb-in-thread-dump-file-tp4705450.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.