[
https://issues.apache.org/jira/browse/QPID-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie reopened QPID-1864:
----------------------------------
Hi Rafi, The new test you added is highlighting a race condition in the 0-8
code path.
This is the error log:
Exception in thread "Dispatcher-Channel-1" java.lang.IllegalStateException:
dispatcher is not started
at org.apache.qpid.client.AMQSession.dispatch(AMQSession.java:2696)
at
org.apache.qpid.client.message.UnprocessedMessage.dispatch(UnprocessedMessage.java:55)
at
org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:2827)
at java.lang.Thread.run(Thread.java:619)
I'll attach the full .out file aswell. Can you take a look and see if the 0-10
change you made would also apply to 0-8?
Cheers
> 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
>
>
> 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]
