activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Snyder (JIRA)" <>
Subject [jira] Updated: (AMQ-2484) Avoid stuck messages in a network of brokers
Date Sat, 18 Sep 2010 16:47:20 GMT


Bruce Snyder updated AMQ-2484:

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> Avoid stuck messages in a network of brokers
> --------------------------------------------
>                 Key: AMQ-2484
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>         Environment: all
>            Reporter: Andreas Gies
>            Priority: Minor
>             Fix For: 5.5.0
> In certain fail over scenarios messages can become "stuck" in a network of brokers. This
would be the case if the message was forwarded to a broker because a consumer existed, but
the consumer disconnects or dies before the message can be delivered. Th then the consumer
reconnects to the network of brokers it might be, that it connects to another member of the
NWOB alltogether. 
> If the message has already passed that other broker on its way, the message is stuck.

> To solve this I was thinking along the lines of allowing a NWOB-redelivery policy. The
default for this could be "NONE" and would represent the current behavior. On top of that
it would be nice to configure a timeout, after which the message will be passed on even to
nodes that it has already crossed. Perhaps some kind of backoffmultiplier would make sense
here as well ?
> Another way might be to simply "forget" the path the message came across, but I am not
sure about the potential impacts regarding duplicate messages or similar issues. 

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

View raw message