[QPID-4922] If Consumer close() method is invoked while inside onMessage(), it should be excuted after onMessage() has completed.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14, 0.16, 0.18, 0.20, 0.22
• Component/s: JMS AMQP 0-x
• Assignee: Rajith Muditha Attapattu
• Reporter: Rajith Muditha Attapattu
• Created: 13/Jun/13 17:30
• Updated: 10/Feb/15 09:46
• Resolved: 10/Feb/15 09:46

Description

If Consumer close() is called while inside onMessage(), it deadlocks (or will be waiting on a condition that would never be true with the patch for QPID-4574).
As per the JMS spec, the consumer cannot be closed() until onMessage() method returns.
Therefore the best solution is to mark that close() has been called and then execute those method once the thread returns from onMessage().

Issue Links

• is part of: QPID-6374 [Java Client] Eliminate deadlocks by acquiring locks in a consistent order
• relates to: QPID-4906 If Session close() or closed() method is invoked while inside onMessage(), they should be excuted after onMessage() has completed.