activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Moran (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2155) ActiveMQ with STOMP producer, multiple consumers -- ActiveMQ doesn't distribute messages to additional consumers.
Date Tue, 10 Mar 2009 22:38:39 GMT

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

Brian Moran updated AMQ-2155:
-----------------------------

    Attachment: stomplog-1.log

Note that there two consumers initially connected, denoted by port - 55213, 55218. 
They process a number of messages, until 15:03:01,555 when 55305 connects/subscribes followed
by 55309 then 55312, 55315,55318, 55324, etc.

NO messages are processed by any of the new consumers until the queue empties at 15:06:34.

A new batch of messages is queued at 15:20:13; this new set is distributed among the waiting
consumers.


> ActiveMQ with STOMP producer, multiple consumers -- ActiveMQ doesn't distribute messages
to additional consumers.
> -----------------------------------------------------------------------------------------------------------------
>
>                 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
>         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.


Mime
View raw message