Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
2.18.0
-
None
-
None
-
I attach the two broker.xml files (renamed because they are slightly different), the other files are the standard files (with a role called 'guest')
Description
I have a test setup with two statically clustered brokers. A JMS producer sends messages to a queue called exampleQueue on broker1, and a Spring Boot JMS listener consumes from a queue with the same name on broker0. The address has the same name, the usernames and password for producer and consumer are identical, as is the user role.
We are currently using ActiveMQ but look to Artemis for the future, and it's important that we can simply change the connection url and queue names for it to work. Code changes are not allowed.
I managed to get the messages bridged from broker1 to broker0 using a core bridge, but I don't want to have to do that for every queue we need to have bridged. The whole point is to have our current central broker split up in multiple brokers according to functional area, and to allow easy inter-area communication using a store-and-forward pattern across brokers.
According to the documentation it should just work, even though on broker1 (where messages are first written to) there is no consumer, that one is connected to broker0. Looking at the two consoles I see this as well. The queue has messages but no consumers, and on broker0 there are two consumers and no messages.