AMQ does not drop connection on stomp client ungraceful shutdown

we have an AMQ 5.3.2. running on server-1 and two perl stomp consumers on server-2 and server-3 consuming from the same queue. I have 10 messages that are being consumed (5 by each consumer) when I shutdown one consumer gracefully, the other consumer gets the messages instantly. Heres the issue -

Producer blocked even after termination of all subscribers

Hi, I'm using ActiveMQ 5.5.0 communicate over a topic and after I follow the steps below my producer blocks. 1. Start two durable subscribers 2. Start producer 3. Start a slow non-durable subscriber 4. Stop the two durable subscriber 5. Wait for the producer to block (and get the log "Usage Man

Embedded Broker with STOMP example

I have a maven project embedding a broker using Spring XML / XBean with the STOMP transport configured. Any help would be greatly appreciated! Logging indicates the broker starts and the STOMP transport has started on the configured port. However, using the STOMP example in the ActiveMQ 5.5 do

Re: Fwd: Message groups enhancement feature request

So it sounds like the current Message Groups behaviour is fine; its just you want to ensure fair load balancing of the message groups across consumers right? So if lots of other clients are restarted; the long running clients could end up claiming too many of the message groups? I wonder if just r

Re: Fwd: Message groups enhancement feature request

Martin, message groups (by design) guarantee that only a single consumer will process messages for a group at a time. It preserves ordering of related/group messages by single threading their processing while still allowing concurrent processing of the queue as a whole (each group has it's own thr

Re: Master/Slave configuring clients

Can anyone reply pls? This is an urgent issue for us. Thanks. -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-configuring-clients-tp3630225p3638168.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Durable subscriptions not surviving network disconnect

Thanks Gary. I'm using ConnectionInfo and RemoveInfo to detect (re)connections. However, I'm trying to tell the client to (re)subscribe againt to the topic, like if I restarted the whole client, but it's not working. I've been playing with TransportListener and some advisory message (don't know w

Re: Fwd: Message groups enhancement feature request

Hi, My issue is that in a dynamically load-balancing scenario with scaling the number of consumers up/down, long-living consumers will tend to gather all available message groups and newly created won't have anything available. Even if a newly created consumer gets a new message group, it will onl