[AMQ-2647] ActiveMQ.Advisory.Connection only forwards logoff information in network of brokers

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.3.0
• Fix Version/s: 5.x
• Component/s: Connector

Environment

ActiveMQ 5.3 running on ubuntu, using NMS 1.2 trunk version

• Assignee: Unassigned
• Reporter: Michel Van Hoof
• Created: 11/Mar/10 11:49
• Updated: 13/Mar/22 14:02
• Resolved: 13/Mar/22 14:02

Description

We use ActiveMQ.Advisory.Connection for logon/off information about clients. during tests this worked fine but now while setting up our production enviroment, we noticed something strange.

We have the following Configuration:

Site 1

Broker A & Broker B ( master slave)

both have a network connection to broker C

Site 2

Broker C - Public broker for external clients

Our services are consuming and producing on Broker A / B on site 1

our clients connect to Broker C and consume / produce there.

When a client connects, no Advisory message is send over the network of brokers ( The message IS send on the local broker so if we consume straight from there, it works)

When a client Disconnects, the advisory message is forwarded in the network of brokers and reaches our consumer...

I'm not 100% sure this is a bug but the behaviour is rather strange. I would think that either NONE of the advisories are sent through the network, or all of them.