[
https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2923.
-----------------------------
Resolution: Not A Problem
Fix Version/s: 5.6.0
updated the doc: Message Ordering
https://cwiki.apache.org/confluence/display/ACTIVEMQ/Stomp
to reflect the possibility of order inversion from a stomp client perspective.
Ordering is based on the producer id generated at connection time.
> Clients are sent messages out of producer-order
> -----------------------------------------------
>
> Key: AMQ-2923
> URL: https://issues.apache.org/jira/browse/AMQ-2923
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0, 5.4.1, 5.4.2
> Environment: Ubuntu 10.04.
> Reporter: James Green
> Assignee: Gary Tully
> Priority: Critical
> Fix For: 5.6.0
>
> Attachments: amq.gif, stomp.log
>
>
> On a single host:
> Producer P1 posts message M1 to Queue Q.
> Producer P2 posts message M2 to Queue Q a few seconds later.
> Consumer C1 comes a few seconds further along along and begins reading from
> Queue Q. Occassionally, C1 receives M2 before M1.
> This is what I'm seeing in two PHP application connecting to ActiveMQ via
> STOMP. After dozens of tests I've finally reproduced it with trace=true. I am
> not sure what environmental conditions cause this to occur.
> I will attach a log. Watch for destination:/queue/Outbound.Account.200000
> which is Q. M1 has a reason="MJINITIALSTATE" and M2 has a
> reason="E----:Confirmed..."
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
