[QPID-7388] [0-10] Client may not respond with a SessionDetached in response to ExecutionException being closed by peer

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: qpid-java-6.1
• Fix Version/s: Future
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 11/Aug/16 17:13
• Updated: 04/Jan/17 15:58
• Resolved: 04/Jan/17 15:58

Description

TransactionTimeoutTest failed https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-MMS-TestMatrix/3241/jdk=JDK%201.7%20(latest),label=ubuntu,profile=java-mms.0-10/artifact/trunk/systests/target/surefire-reports/java-mms.0-10/TEST-org.apache.qpid.test.unit.transacted.TransactionTimeoutTest.testProducerOpenCommitTwice.txt in the following manner:

org.apache.qpid.test.unit.transacted.TransactionTimeoutTest.testProducerOpenCommitTwice

Failing for the past 1 build (Since Failed#3241 )
Took 1 min 3 sec.
Error Message

Should have caught exception in listener
Stacktrace

junit.framework.AssertionFailedError: Should have caught exception in listener
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.assertTrue(Assert.java:22)
	at junit.framework.TestCase.assertTrue(TestCase.java:192)
	at org.apache.qpid.test.unit.transacted.TransactionTimeoutTestCase.check(TransactionTimeoutTestCase.java:214)
	at org.apache.qpid.test.unit.transacted.TransactionTimeoutTest.testProducerOpenCommitTwice(TransactionTimeoutTest.java:214)

Examination of the logs (attached), show that the Broker sent an ExecutionException(errorCode=RESOURCE_LIMIT_EXCEEDED, description=Open transaction timed out) and then followed with other session commands including a SessionDetatch. The client failed to report the exception to the application (test) by way of a JMSException from the #commit() call. It also hung, seemingly trying to close the session itself. The problem suggests a client side race, but I have not investigated further.

Perhaps the Broker change - QPID-7374 - has somehow brought this defect out?