You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Brad Willard (JIRA)" <ji...@apache.org> on 2010/04/07 20:37:08 UTC

[jira] Created: (AMQ-2688) Filtering with JMSCorrelationID violates Message Order.

Filtering with JMSCorrelationID violates Message Order.
-------------------------------------------------------

                 Key: AMQ-2688
                 URL: https://issues.apache.org/activemq/browse/AMQ-2688
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.3.0
         Environment: Centos 5, ActiveMQ 5.3.0
            Reporter: Brad Willard


I am using correlation to send messages to different consumers.  The message producer knows the id for each consumer, and always puts a message on a queue for each consumer using the appropriate correlationid in the message.  If there are three consumers, it puts on three messages, each with a correlationid for the intended consumer and calls commit.  What I've noticed is that the consumers (using either MessageListener or explicitly calling receive) will sometimes get the messages out of order.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (AMQ-2688) Filtering with JMSCorrelationID violates Message Order.

Posted by "Brad Willard (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Willard closed AMQ-2688.
-----------------------------

    Resolution: Working as Designed

Threading bug in my producer code.

> Filtering with JMSCorrelationID violates Message Order.
> -------------------------------------------------------
>
>                 Key: AMQ-2688
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2688
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>         Environment: Centos 5, ActiveMQ 5.3.0
>            Reporter: Brad Willard
>
> I am using correlation to send messages to different consumers.  The message producer knows the id for each consumer, and always puts a message on a queue for each consumer using the appropriate correlationid in the message.  If there are three consumers, it puts on three messages, each with a correlationid for the intended consumer and calls commit.  What I've noticed is that the consumers (using either MessageListener or explicitly calling receive) will sometimes get the messages out of order.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.