Kevin Goerlitz created AMQ-7515:
-----------------------------------
Summary: Networked broker does not pass along queue consumer upon
reconnect
Key: AMQ-7515
URL: https://issues.apache.org/jira/browse/AMQ-7515
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.15.13, 5.15.10
Environment: ContOS 7 based docker image with Java 8.
Reporter: Kevin Goerlitz
We have a hub-spoke broker network with about 40 spokes. when restarting the
hub broker, the spoke brokers reconnect. However, when some of the spoke
brokers reconnect, they do not pass along the consumer of one of the queues to
the hub. Messages the the queue are queued up and are not delivered until
either the client app is restarted or the spoke broker is restarted (which will
cause the client app to reconnect).
It is usually the same set of spoke brokers that do not pass on the consumer.
Each spoke broker has 5-8 consumers and it is always the consumer for the same
app that is not passed on (the queue is different for each remote system). The
spoke broker still has the consumer active.
The brokers are stand-alone and the client apps are using the STOMP protocol.
The spoke brokers are connected to the hub via a duplex connection initiated by
the spoke.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
