Are the connection advisory messages forwarded across a network of brokers?
Solution 1:
As I did not tried by myself, I firstly though the Advisory topics are treated as other topics but it seems not to be the case as explained in this post
The documentation on the Advisory topics does not mentions this and the above post is written by an ActiveMQ developer which seems to be a reliable source.
When connecting to Advisory topics, you have to be careful if you have authorization in place: you must give read/write access to all clients to the Advisory Topics like said in the security doc. This SO question relates exactly the issue you can have by not configuring properly the security.
On your side, I would recommend to create a network of broker with e.g. a Docker Compose and test it locally.
Further useful readings:
- https://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-Networksofbrokersandadvisories
- https://dzone.com/articles/how-monitor-activemq-networks
- https://dzone.com/articles/active-mq-network-brokers
- https://blog.christianposta.com/activemq/from-inside-the-code-activemq-network-bridges-and-demand-forward-subscriptions
- https://activemq.apache.org/advisory-message.html
- https://activemq.apache.org/components/cms/tutorials/handling-advisory-messages
- https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/ensuring-effective-amazon-mq-performance.html#network-of-brokers-configure-correctly