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

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-2647:
----------------------------

    Fix Version/s:     (was: 5.5.0)
                   5.6.0

> ActiveMQ.Advisory.Connection only forwards logoff information in network of brokers
> -----------------------------------------------------------------------------------
>
>                 Key: AMQ-2647
>                 URL: https://issues.apache.org/jira/browse/AMQ-2647
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.3.0
>         Environment: ActiveMQ 5.3 running on ubuntu, using NMS 1.2 trunk version
>            Reporter: Michel Van Hoof
>             Fix For: 5.6.0
>
>
> 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. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira