I'm working on an application where we want to monitor logon/logoff of clients. Since ActiveMQ contains Advisory Topics that alert you of new connections and removal of connections, the idea was to use this advisory messages ( ActiveMQ.Advisory.Connection). This worked fine during development but now, when we are going to production in our network of brokers, we noticed that the messages from remote brokers in the network are not getting to our consumer.
Our setup is:
Producer | Broker A and B ( master Slave) in site 1 -> These have a duplex network connector to our public brokers (C & D)
Broker C and D (master slave again) in site 2
and attached to C and D, we have the "consumers" of whom we want to know logon/logoff information.
When we take a look at the advisory topic in the admin console on Broker A, we see the subscriber and we get logon messages if we let a consumer connect. On Broker C, I don't see any subscribers on the advisory topic, and when a consumers logs on / OFF, we don't see the advisory message.
Is this behaviour by default or am i missing a config?