[
https://issues.apache.org/activemq/browse/AMQ-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-2324:
----------------------------
Fix Version/s: (was: 5.3.0)
5.4.0
This behavior won't be changed for 5.3 as we need to finalize this release
asap. Suppression of forwarded messages back to their origin is there to
prevent looping in this case, but it could be implemented with loop detection
and ttl and possibly with periodic backoff and also using some of the logic you
describe.
> Forwarded message cannot be distributed to the original broker
> --------------------------------------------------------------
>
> Key: AMQ-2324
> URL: https://issues.apache.org/activemq/browse/AMQ-2324
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: ying
> Fix For: 5.4.0
>
>
> I have a simple cause which can cause dispatch problem:
> 1. setup a network of broker1, broker2, bridged by multicast discovery
> 2. make a producer send 5 msg to queueA to broker2
> 3. make a consumer to consume from broker1 queueA ( make it slow, so it only
> consumer 1 msg) but make sure all 5 msg from broker2 are forwared to broker1
> 4. stop the consumer to broke1, restart it to consume from broker2 queueA
> 5. the 4 msgs originally published to broker2 and forwarded to broker1 and
> has not yet been consumed will stuck on broker1 and will not forwarded to
> broker2 for the consumer to consume.
> Here is an solution: it checks forwarded to broker( eg, broker1) to see
> whether it has any active consumer, it will be able forward the message back
> to the original broker when there is no active consumer on the forwarded to
> broker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
