Jean-Baptiste Onofré created AMQ-7316:
-----------------------------------------
Summary: Network connector is not able to handle bunch of
destinations
Key: AMQ-7316
URL: https://issues.apache.org/jira/browse/AMQ-7316
Project: ActiveMQ
Issue Type: Bug
Components: Broker, networkbridge
Affects Versions: 5.15.10, 5.15.9, 5.11.1
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
In a setup where we have a lot of destinations (let say ~ 1000 queues) on a
dynamic network connector, we are loosing/delay the advisory messages (for
instance when a client consumes from a queue).
That's cause issue on the network bridge and we can see (on JMX or wenconsole)
that we can have "stale" active bridge consumer on a queue whereas the bridge
remote broker don't have any consumer.
We have to improve the number of destinations managed on bridges.
There are four workarounds for this issue:
1. reduce the number of destinations. Obviously, if we have less destination
count (topics or queues), there's no bottleneck on the advisory messages.
2. use {{decreaseNetworkPriority}} to limit the number of advisory and prefer
local consumers.
3. use a static network of brokers instead of dynamic
4. create several network connectors, each one dealing with subset of queues
(using {{dynamicallyIncludedDestinations}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
