[
https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPIDJMS-239:
-------------------------------
Comment: was deleted
(was: Sure, I'll try to do this in the next day to two.)
> Client ack session occasionally seen to redeliver recovered messages out of
> order
> ---------------------------------------------------------------------------------
>
> Key: QPIDJMS-239
> URL: https://issues.apache.org/jira/browse/QPIDJMS-239
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.11.0, 0.20.0
> Reporter: Keith Wall
> Attachments:
> TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.txt,
>
> TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt,
>
> TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0_proton.txt
>
>
> Test org.apache.qpid.test.unit.ack.RecoverTest#testOrderingWithAsyncConsumer
> [1] fails occasional when run against the Java Broker. The test publishes a
> number of messages then uses an async message listener to consume them. For
> each message, the message listener recovers the session five times before
> finally acknowledging the message, then the cycle repeats. In failure case,
> I see the Qpid JMS Client delivery an unexpected message to the application
> after a sequence of expected.
> We have seen the failure on the Apache CI and I can reproduce the problem on
> my laptop (every 15-20 runs of the test).
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-MMS-1.0/40/artifact/trunk/systests/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.txt
> I have reproduced locally against 0.20.0 too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
