activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michel Van Hoof (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2647) ActiveMQ.Advisory.Connection only forwards logoff information in network of brokers
Date Sat, 18 Sep 2010 16:57:44 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61898#action_61898
] 

Michel Van Hoof commented on AMQ-2647:
--------------------------------------

Geachte,

Ik ben momenteel niet op kantoor en heb slechts beperkte toegang tot mijn e-mail. Ik ben terug
bereikbaar op maandag 4/10.

Voor dringende zaken kan u mijn collega Johan Verelst bereiken via jverelst@thisplays2.com
of via telefoon op  32 3 327 92 99

Met Vriendelijke groeten,

Michel Van Hoof

----------------------------------------------------------------------------------------

I am currently out of the office and have limited  access to my e-mail. I will return on monday
the 4th of October.

For urgent mathers, please contact jverelst@thisplays2.com or by phone on  32 3 327 92 99

Kind regards,

Michel Van Hoof


> ActiveMQ.Advisory.Connection only forwards logoff information in network of brokers
> -----------------------------------------------------------------------------------
>
>                 Key: AMQ-2647
>                 URL: https://issues.apache.org/activemq/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.5.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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message