You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Abhi (JIRA)" <ji...@apache.org> on 2015/04/02 15:29:28 UTC

[jira] [Commented] (AMQ-5705) originBrokerURL incorrectly set in advisory messages

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

Abhi commented on AMQ-5705:
---------------------------

What kind of issues can be triggered by this?

> 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)