[QPID-6264] ExternalACL#testAccessVirtualHostWithName fails owing to race condition on connection close

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 0.31
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 05/Dec/14 16:07
• Updated: 19/Mar/15 12:23
• Resolved: 14/Feb/15 08:46

Description

ExternalACL#testAccessVirtualHostWithName test fails with assertion failure:

Error Message

Unexpected exception message expected:<...reating connection: [Permission denied: test]> but was:<...reating connection: [Socket closed]>
Stacktrace

junit.framework.ComparisonFailure: Unexpected exception message expected:<...reating connection: [Permission denied: test]> but was:<...reating connection: [Socket closed]>
	at junit.framework.Assert.assertEquals(Assert.java:100)
	at junit.framework.TestCase.assertEquals(TestCase.java:261)
	at org.apache.qpid.server.security.acl.ExternalACLTest.assertAccessDeniedException(ExternalACLTest.java:78)
	at org.apache.qpid.server.security.acl.ExternalACLTest.testAccessVirtualHostWithName(ExternalACLTest.java:108)

It seems that there is a race condition. If the Broker closes the socket before the client has reported the connection close reason back to the client, the cause of the connection close is lost.

Issue Links

• duplicates: QPID-6350 [AMQP0-10] Original connection exception lost if Broker closes socket before client