[QPID-2345] Java Client not detecting cause of session close from client thread

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Later
• Affects Version/s: 0.6
• Fix Version/s: JIRA Cleanup
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Martin Ritchie
• Created: 19/Jan/10 20:22
• Updated: 05/Sep/11 21:45
• Resolved: 05/Sep/11 21:45

Description

As exemplified by the SimpleACLTest when the broker closes the connection the client attempts to stop the current activity and remember the cause of the closure to report to the client. However, if the client is in the process of performing a operation such as session.createQueue() the closed state can be deteted before the cause has been set as a result the IllegalStateException is thrown and no cause has been set.

This was working on 0.5. However, it is possible that the new IO layer is highlighting another race condition. Or that it is not correctly setting the state to CLOSED. Which is required to be done to prompt the client threads to check for a causal exception.

Issue Links

• relates to: QPID-2262 Random test failures in SimpleACLTest
• relates to: QPID-3339 Occasional test failures from ExternalACLTest under java.0.10