[AMQ-5535] deadlock on close and failover reconnect around org.apache.activemq.ActiveMQConnection.getScheduler

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.10.0
• Fix Version/s: 5.11.0
• Component/s: JMS client, Transport
• Labels: failover

Environment

failover

• Regression: Unit Test Broken
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 23/Jan/15 12:12
• Updated: 23/Jan/15 13:11
• Resolved: 23/Jan/15 13:11

Description

Hung test - org.apache.activemq.transport.failover.FailoverUpdateURIsTest

deadlock:

Name: ActiveMQ Transport: tcp://localhost/127.0.0.1:61616@51978
State: BLOCKED on org.apache.activemq.ActiveMQConnection@2ccf4c0e owned by: main
Total blocked: 3  Total waited: 1

Stack trace: 
org.apache.activemq.ActiveMQConnection.getScheduler(ActiveMQConnection.java:2554)
org.apache.activemq.ActiveMQSession.clearMessagesInProgress(ActiveMQSession.java:687)
org.apache.activemq.ActiveMQConnection.transportInterupted(ActiveMQConnection.java:2043)
org.apache.activemq.transport.TransportFilter.transportInterupted(TransportFilter.java:105)
org.apache.activemq.transport.TransportFilter.transportInterupted(TransportFilter.java:105)
org.apache.activemq.transport.failover.FailoverTransport.handleTransportFailure(FailoverTransport.java:279)
   - locked java.lang.Object@6242de17
org.apache.activemq.transport.failover.FailoverTransport$3.onException(FailoverTransport.java:216)
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160)
org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200)
java.lang.Thread.run(Thread.java:745)

–

Name: main
State: BLOCKED on java.lang.Object@6242de17 owned by: ActiveMQ Transport: tcp://localhost/127.0.0.1:61616@51978
Total blocked: 18  Total waited: 1,043

Stack trace: 
org.apache.activemq.transport.failover.FailoverTransport.oneway(FailoverTransport.java:572)
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1331)
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1325)
org.apache.activemq.AdvisoryConsumer.dispose(AdvisoryConsumer.java:57)
   - locked org.apache.activemq.AdvisoryConsumer@3a6d125b
org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:660)
   - locked org.apache.activemq.ActiveMQConnection@2ccf4c0e
org.apache.activemq.transport.failover.FailoverUpdateURIsTest.tearDown(FailoverUpdateURIsTest.java:52)
junit.framework.TestCase.runBare(TestCase.java:146)
junit.framework.TestResult$1.protect(TestResult.java:122)
junit.framework.TestResult.runProtected(TestResult.java:142)
junit.framework.TestResult.run(TestResult.java:125)
junit.framework.TestCase.run(TestCase.java:129)
junit.framework.TestSuite.runTest(TestSuite.java:255)
junit.framework.TestSuite.run(TestSuite.java:250)
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

Issue Links

• is related to: AMQ-3714 getScheduler():Scheduler of class org.apache.activemq.ActiveMQConnection should use lazy initialisation