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 2010/09/16 17:22:40 UTC
[jira] Created: (AMQ-2923) Clients are send messages out of
producer-order
Clients are send 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
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.
[jira] Commented: (AMQ-2923) Clients are sent messages out of
producer-order
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (AMQ-2923) Clients are send messages out of
producer-order
Posted by "James Green (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Green updated AMQ-2923:
-----------------------------
Attachment: stomp.log
Stomp trace showing a two messages received to a single queue, being sent in reverse order.
> Clients are send 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.
[jira] Updated: (AMQ-2923) Clients are sent messages out of
producer-order
Posted by "James Green (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Green updated AMQ-2923:
-----------------------------
Summary: Clients are sent messages out of producer-order (was: Clients are send messages out of producer-order)
> 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.