[
https://issues.apache.org/jira/browse/ARTEMIS-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443639#comment-17443639
]
Anton Roskvist commented on ARTEMIS-3557:
-----------------------------------------
Hi,
It might very well be by design, but at least I find the behavior a bit
unintuitive. Connecting a client to a cluster you should not have to know where
other clients are connected to be able to receive messages, regardless of them
being multicast or not. That might just be me though, I'll accept that
possibility :). I did add a condition on the #matchBinding that solves this for
specifically OFF_WITH_REDISTRIBUTION.
For 2 I do believe my PR solves that scenario, at least from what I can tell.
The addition to PostOfficeImpl adds a redistributor when setting up a local
binding (if there are remote consumers set up for it), as well as when a new
remote consumer is added. This operation could probably be done better (with
fewer steps) but I have yet to figure out how.
Br,
Anton
> ARTEMIS-1925 fix does not handle Multicast in cluster and redistribution to
> "old" consumers
> -------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3557
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3557
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> OFF_WITH_REDISTRIBUTION does not handle two scenarios:
> 1. non durable Multicast where the subscriber is on a separate node from the
> publisher. Messages gets dropped.
> 2. If a destination and consumer exist on one node in a cluster and a
> producer shows up on another node messages will not get redistributed until
> the old consumer disconnects and reconnects.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
