Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.22
-
None
Description
I have run the java systests with the JCarder agent attached. When using AMQP 0-9, JCarder detected a potential deadlock when the following are done concurrently:
- Close a consumer from an application thread.
- Call Connection.createSession from an application thread.
- Call Connection.createSession inside MessageListener.onMessage().
Here is a sketch of the deadlock scenario:
"Dispatcher-1-Conn-780" AMQSession$Dispatcher.dispatchMessage() lock AMQSession.this._messageDeliveryLock AMQConnection.createSession() lock AMQConnection._sessionCreationLock BLOCKED BY applicationThread1 "applicationThread1" AMQConnection.createSession lock AMQConnection._sessionCreationLock ... AMQConnectionDelegate_8_0.executeRetrySupport lock AMQConnection.getFailoverMutex() BLOCKED BY applicationThread2 "applicationThread2" BasicMessageConsumer.close() lock AMQSession.getFailoverMutex() lock AMQSession._messageDeliveryLock BLOCKED BY Dispatcher-1-Conn-780
Interestingly, AMQConnectionDelegate_0_10.executeRetrySupport(..) does not acquire the failover mutex (I have no idea if it should) so is not susceptible to this deadlock.
I've attached the GraphViz .dot file that JCarder generated when it detected this problem.
Note that this problem is similar to QPID-4574 and QPID-5118 so might be fixed by a single commit.
Attachments
Attachments
Issue Links
- is part of
-
QPID-6374 [Java Client] Eliminate deadlocks by acquiring locks in a consistent order
- Closed