You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/08/11 17:27:20 UTC
[jira] [Updated] (QPID-7388) [0-10] Client may not respond with a
SessionDetached in response to session being closed by peer
[ https://issues.apache.org/jira/browse/QPID-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7388:
-----------------------------
Summary: [0-10] Client may not respond with a SessionDetached in response to session being closed by peer (was: []0-10] Client may not respond with a SessionDetached in response to session being closed by peer)
> [0-10] Client may not respond with a SessionDetached in response to session being closed by peer
> ------------------------------------------------------------------------------------------------
>
> Key: QPID-7388
> URL: https://issues.apache.org/jira/browse/QPID-7388
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: qpid-java-6.1
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.unit.transacted.TransactionTimeoutTest.testProducerOpenCommitTwice.txt
>
>
> {{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:
> {noformat}
> 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)
> {noformat}
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org