activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <hi...@hiramchirino.com>
Subject Re: Network of brokers and starvation problem
Date Mon, 22 May 2006 15:14:05 GMT
There is a TTL setting on the network connector the limits the number
of broker hops a messages is allowed to take.  By default it is set to
1.  This prevents a message from ever looping around nodes in a
network.

You could change the setting to be higher, but be advised that you
risk having messages loop.

On 5/22/06, Mathias Herberts <mathias.herberts@gmail.com> wrote:
> Hi,
>
> I have set up a network of two brokers (which connect bidirectionnaly
> to each other after discovering themselves via multicast).
>
> Broker A talks to broker B and B talks to A.
>
> Consumer C1 is connected to B, subscribing to a queue Q.
> Producer P1 connects to A and posts a message M to a queue Q.
> C1 receives M, then dies without committing/acking M.
> Consumer C2 connects to B and subscribes to Q.
> C2 will NEVER receive M thus leading to a starvation situation.
>
> Shouldn't the connection of a consumer to a broker part of a network
> of brokers trigger an event sent to all brokers part of the network
> and forcing brokers with messages for a given destination and no
> consumer for that destination to forward the messages back to a broker
> with consumers?
>
> Mathiias.
>


-- 
Regards,
Hiram

Mime
View raw message