[
https://issues.apache.org/jira/browse/QPID-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711626#action_12711626
]
Rafael H. Schloming commented on QPID-1864:
-------------------------------------------
Hmm, I suspect the dispatcher thread exception may be unrelated to the test
failure. I think I've seen that same dispatcher thread exception on successful
runs.
Regarding the test failure, the appropriate fix is dependent on the desired
requeue semantics for the java broker. For the cpp broker, released messages
are requeued at the head of the queue, so the order that messages are released
determines the order in which they are placed back on the queue. If the java
broker does something similar for 0-8 "rejected" messages, then I should be
able to make a very similar change to the 0-8 rollback code.
> java 0-10 client sometimes releases messages in non queue order on rollback
> ---------------------------------------------------------------------------
>
> Key: QPID-1864
> URL: https://issues.apache.org/jira/browse/QPID-1864
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6
> Reporter: Rafael H. Schloming
> Assignee: Rafael H. Schloming
> Fix For: 0.6
>
> Attachments:
> TEST-org.apache.qpid.test.client.RollbackOrderTest.testOrderingAfterRollback.out
>
>
> On rollback, the java client sometimes releases messages from the dispatch
> thread. These messages are released in an unpredictable order relative to the
> messages released from the main thread. Also, the messages released from the
> BMC.rollbackPendingMessages() are released individually and in the opposite
> order of what would preserve queue order in a single consumer scenario.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]