Christopher L. Shannon created AMQ-9689:
-------------------------------------------
Summary: Network of Broker durable sync TTL fixes and improvements
Key: AMQ-9689
URL: https://issues.apache.org/jira/browse/AMQ-9689
Project: ActiveMQ Classic
Issue Type: Bug
Affects Versions: 6.1.6, 5.19.0
Reporter: Christopher L. Shannon
Assignee: Christopher L. Shannon
Fix For: 6.2.0
Some recent testing has shown a few issues related to the syncing and
reactivation of durable subscriptions over a network of brokers related to TTL.
The following updates are being made:
# A fix for a bug during durable subscription reactivation when dynamicOnly is
false that would cause the clientId to not be included in the consumer advisory
which could cause a loop to be created as the other broker would not be able to
tell where the network subscription came from.
# During reactivation and sync, when {{dynamicOnly}} is false and durable sync
is set to true, we should make sure to include the TTL information (full broker
path) from the online consumer attached to durables so that TTL info is
properly propagated so we don't incorrectly create demand. This only works if
consumers are online, so for TTL > 1 it is still recommended to set dynamicOnly
to true and allow only online consumers drive demand.
# For TTL 1, we can handle sync correctly on restarts even if durables are
offline and missing consumer TTL info because we know that we should ignore
proxy durables (bridge durables for other bridges) entirely because they will
be > 1 hop away.
# Some other minor improvements were made like filtering everything if TTL is 0
and also consolidating logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
