activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vu Le (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5705) originBrokerURL incorrectly set in advisory messages
Date Thu, 02 Apr 2015 17:12:52 GMT

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

Vu Le commented on AMQ-5705:
----------------------------

Actually, this is an issue for us. We are capturing metrics from the advisory messages and
this is causing our metrics to be off.

> originBrokerURL incorrectly set in advisory messages
> ----------------------------------------------------
>
>                 Key: AMQ-5705
>                 URL: https://issues.apache.org/jira/browse/AMQ-5705
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.11.1
>            Reporter: Vu Le
>            Priority: Minor
>
> With a broker configured with multiple transports, the "originBrokerURL" property of
advisory messages is incorrectly set. 
> Assuming a broker that has two transports configured, an advisory message for a connection
made to transport-A may have the "originBrokerURL" property set to transport-B.
> Looks like the "originBrokerURL" value is set from the getDefaultSocketURIString() method
in the BrokerService class. Is there a good reason why the "originBrokerURL" value does not
correlate with the transport where the advisory event is actually being triggered?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message