[jira] Updated: (AMQ-2155) ActiveMQ with STOMP producer, multiple consumers -- ActiveMQ doesn't distribute correct messages to additional consumer AND Delivers messages out of order to newly connecting consumer.

["Rob Davies (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-2155:
----------------------------

    Fix Version/s: 5.4.0

> ActiveMQ with STOMP producer, multiple consumers -- ActiveMQ doesn't distribute correct messages to additional consumer AND Delivers messages out of order to newly connecting consumer.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2155
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2155
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0, 5.2.0
>         Environment: mac osx; rails 2.1.1; ruby 1.8.6;
>            Reporter: Brian Moran
>            Priority: Critical
>             Fix For: 5.4.0
>
>         Attachments: stomplog-1.log
>
>
> Using the stock ActiveMQ 5.2.0 install, with a very small producer and consumer (see source code here: http://groups.google.com/group/activemessaging-discuss/browse_thread/thread/0b45ae6f030a13af#) , using client :ack mode;
> Adding additional consumers to a queue results has no affect on message distribution -- only the originally connected consumers receive the messages UNTIL the queue is empty, or the original message consumes disconnect. One would LIKE to be able to add additional consumers for a queue, and have the broker distrubute messages to those consumers -- this does NOT happen in 5.1.0 and 5.2.0.  
> ALSO, when there are multiple consumers attached to the broker, performance can degrade so that only one or two consumers are being sent messages. THIS may be related, perhaps not.
> ATTACHED is a dump of the STOMP TRANSPORT trace. 

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