You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "James Green (JIRA)" <ji...@apache.org> on 2011/01/07 13:49:45 UTC
[jira] Updated: (AMQ-2923) Clients are sent messages out of
producer-order
[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Green updated AMQ-2923:
-----------------------------
Attachment: amq.gif
Screenshot showing web console with messages listed out of order. Notice 90 seconds between timestamps!
> 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
> Affects Versions: 5.4.0
> Environment: Ubuntu 10.04.
> Reporter: James Green
> Priority: Critical
> 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.
-
You can reply to this email to add a comment to the issue online.