activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2923) Clients are sent messages out of producer-order
Date Thu, 16 Sep 2010 15:57:40 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61874#action_61874
] 

Gary Tully commented on AMQ-2923:
---------------------------------

just a thought, but I think concurrentStoreAndDispatchQueues on the kahaDB persistence adapter
may be the answer here. can you set it to false:
<kahaDB .... concurrentStoreAndDispatchQueues="false" />

> Clients are sent messages out of producer-order
> -----------------------------------------------
>
>                 Key: AMQ-2923
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2923
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.0
>         Environment: Ubuntu 10.04.
>            Reporter: James Green
>            Priority: Critical
>         Attachments: 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.


Mime
View raw message