[
https://issues.apache.org/jira/browse/QPID-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425170#comment-13425170
]
Robbie Gemmell commented on QPID-4171:
--------------------------------------
Renamed JIRA to indicate only persistent messages can be enqueued out of order,
transient messages will always have an immediate future assigned and will thus
enqueue in-order. It is possible for transient messages to overtake persistent
messages, but thats is allowable (though we should have given people the option
to prevent it).
Attached are some helpful scribbles for anyone working on this. It includes a
trivial potential fix (&& !persistent), along with some dead code removal, and
addition of a noddy system property to escape the previously mentioned
'transient can overtake persistent' behaviour when mixing delivery modes. It
semi-duplicates the existing addFuture() method because thats used by more than
just the enqueue methods for things that care nothing of whether its persistent
message or whether strict ordering is desired, so it seemed like it would be a
bit nasty just feeding default parameter values to a shared implementation.
This isn't really a patch as such, it hasn't even been compiled properly
nevermind tested, but I think it should work :)
> persistent messages from a non-transactional session can be enqueued out of
> order
> ---------------------------------------------------------------------------------
>
> Key: QPID-4171
> URL: https://issues.apache.org/jira/browse/QPID-4171
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Broker BDB Store
> Affects Versions: 0.16, 0.18, 0.19
> Reporter: Keith Wall
> Assignee: Keith Wall
> Attachments: QPID-4171-scribbles.txt
>
>
> A defect in AsyncAutoCommitTransaction means that occasionally messages
> delivered by a non-transactional JMS are seen to be enqueued out-of-order and
> therefore delivered to a consumer out of the expected order.
> It is this problem that underlies QPID-4014, although as I think this problem
> is wider than ConflationQueues, I am raising this separately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
