Keith Wall created QPID-6264:
--------------------------------
Summary: ExternalACL#testAccessVirtualHostWithName owing to race
condition on connection close
Key: QPID-6264
URL: https://issues.apache.org/jira/browse/QPID-6264
Project: Qpid
Issue Type: Bug
Reporter: Keith Wall
Fix For: 0.31
ExternalACL#testAccessVirtualHostWithName test fails with assertion failure:
{noformat}
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)
{noformat}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
