KahaDB store - deadlock on shutdown
-----------------------------------
Key: AMQ-2153
URL: https://issues.apache.org/activemq/browse/AMQ-2153
Project: ActiveMQ
Issue Type: Bug
Components: Message Store
Affects Versions: 5.3.0
Reporter: Gary Tully
Fix For: 5.3.0
little bit of deadlock between the shutdown and the checkpoint thread.
{code}
"ActiveMQ Journal Checkpoint Worker" prio=5 tid=0x01016f10 nid=0x8dd800 waiting
for monitor entry [0xb0d8c000..0xb0d8cd90]
at
org.apache.activemq.store.kahadb.MessageDatabase.checkpointCleanup(MessageDatabase.java:468)
- waiting to lock <0x095ad3e0> (a java.lang.Object)
at
org.apache.activemq.store.kahadb.MessageDatabase$3.run(MessageDatabase.java:261)
"main" prio=5 tid=0x010013b0 nid=0xb0801000 in Object.wait()
[0xb07ff000..0xb0800188]
at java.lang.Object.wait(Native Method)
- waiting on <0x0959f608> (a
org.apache.activemq.store.kahadb.MessageDatabase$3)
at java.lang.Thread.join(Thread.java:1113)
- locked <0x0959f608> (a
org.apache.activemq.store.kahadb.MessageDatabase$3)
at java.lang.Thread.join(Thread.java:1166)
at
org.apache.activemq.store.kahadb.MessageDatabase.close(MessageDatabase.java:310)
at
org.apache.activemq.store.kahadb.MessageDatabase.unload(MessageDatabase.java:327)
- locked <0x095ad3e0> (a java.lang.Object)
at
org.apache.activemq.store.kahadb.MessageDatabase.stop(MessageDatabase.java:173)
at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:519)
at org.apache.activemq.JmsTestSupport.tearDown(JmsTestSupport.java:136)
at junit.framework.TestCase.runBare(TestCase.java:130)
at
org.apache.activemq.CombinationTestSupport.runBare(CombinationTestSupport.java:90)
at
org.apache.activemq.CombinationTestSupport.runBare(CombinationTestSupport.java:96)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
