[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882777#comment-15882777 ] Timothy Bish commented on QPIDJMS-239: -- Great, thanks for closing the loop on this. > 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 > Fix For: 0.21.0 > > Attachments: > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0_proton.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.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.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882744#comment-15882744 ] Keith Wall commented on QPIDJMS-239: Hi Tim, Good news. I haven't been able to reproduce the issue against the current 0.21.0-SNAPSHOT. I can reason that as org.apache.qpid.jms.JmsSession#recover internally temporarily stops the session, that QPIDJMS-266 is almost certainly the root cause. Thanks for chasing this one down. > 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 > Fix For: 0.21.0 > > Attachments: > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0_proton.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.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.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872429#comment-15872429 ] Timothy Bish commented on QPIDJMS-239: -- Pretty sure this is the underlying issue. If you could retest with a snapshot build to confirm that'd be great or wait until 0.21.0 which will have this fix. > 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_0.20.0_proton.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.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.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[
https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812176#comment-15812176
]
Keith Wall commented on QPIDJMS-239:
Running {{ConsumerIntegrationTest#testRecoverOrderingWithAsyncConsumer}} does
not reproduce the problem for me. I reconfirmed I see the problem when running
{{org.apache.qpid.test.unit.ack.RecoverTest#testOrderingWithAsyncConsumer}}
against trunk Java Broker with trunk qpid-jms-client. I am on JDK 1.8.0_111 on
a Mac. I have seen the problem once on Apache CI. I'm happy to run with
diagnostic patches in that helps us get to the bottom of this.
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811710#comment-15811710 ] Keith Wall commented on QPIDJMS-239: 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811711#comment-15811711 ] Keith Wall commented on QPIDJMS-239: 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801866#comment-15801866 ] Robbie Gemmell commented on QPIDJMS-239: [~k-wall] could you check if you see this with the ConsumerIntegrationTest#testRecoverOrderingWithAsyncConsumer test I've added? Theres a repetitions toggle on the test itself you can use if you like. If you can, perhaps we can modify that to aid collecting more detail. I still can't see how it could manage this, and I haven't been able to reproduce it with either the original test, Tims version agaisnt ActiveMQ, or the brokerless one above. > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801839#comment-15801839 ] ASF subversion and git services commented on QPIDJMS-239: - Commit 84c95aa1e1f5f9b43e32b490dcc1091b343cde3e in qpid-jms's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=84c95aa ] QPIDJMS-239: add test using the test peer > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767611#comment-15767611 ] ASF subversion and git services commented on QPIDJMS-239: - Commit 81fc0d9a029f297c385f163262821ae056fa5cdc in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=81fc0d9 ] QPIDJMS-239 Add a test against ActiveMQ based on the scenario described Adds a recover test based on the described scenario in the ActiveMQ test suite to try and reproduce. > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[
https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761279#comment-15761279
]
Keith Wall commented on QPIDJMS-239:
Please find attached
(TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0_proton.txt).
On the surface, it appears that the client (or proton-j) is emitting an
unexpected Disposition for a message that the application has not yet seen.
{noformat}
{Disposition{role=RECEIVER, first=7, last=7, settled=true, state=Accepted{},
batchable=false}
{noformat}
Let me know if you need anything else.
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755631#comment-15755631 ] Robbie Gemmell commented on QPIDJMS-239: I had a look at this and couldn't spot how it would happen or reproduce it with a variant of the test I made to isolate the consumer, either with the original counts or while massively increasing the number of messages and recovers used. Could you capture a failing log with the the clients protocol trace logging enabled, in case it can add something to the picture? Last bit on the page from http://qpid.apache.org/releases/qpid-jms-0.11.1/docs/index.html#logging. No rush as I'm actually going to start my holiday now :) > 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 > [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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[
https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751756#comment-15751756
]
Keith Wall commented on QPIDJMS-239:
I've attached two examples. The pattern I see can be summarised with a grep.
The point the unexpected message appears seems to vary.
{format}
grep 'delivery dispatcher'
TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt
2016-12-15 15:58:48,531 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 0 and calling recover
2016-12-15 15:58:48,532 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 0 and calling recover
2016-12-15 15:58:48,533 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 0 and calling recover
2016-12-15 15:58:48,533 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 0 and calling recover
2016-12-15 15:58:48,534 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 0 and calling recover
2016-12-15 15:58:48,536 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Acknowledging message 0
2016-12-15 15:58:48,537 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 1 and calling recover
2016-12-15 15:58:48,540 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 1 and calling recover
2016-12-15 15:58:48,542 DEBUG [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.a.RecoverTest Ignoring message 1 and calling recover
# Qpid JMS Client delivers 7th message rather than redelivering the 1st
2016-12-15 15:58:48,546 ERROR [JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher]
o.a.q.t.u.InternalBrokerHolder Uncaught exception from thread JmsSession
[ID:f702629f-cc27-4366-87a7-55c52282b0cf:1:1] delivery dispatcher
junit.framework.AssertionFailedError: Received Message Out Of Order
expected:<1> but was:<7>
{format}
> 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
> [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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
