[
https://issues.apache.org/jira/browse/AMQ-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5705.
-----------------------------
Resolution: Fixed
fix for test regression in
http://git-wip-us.apache.org/repos/asf/activemq/commit/37c46b9b
transforming vm urls does not make any sense because they container the
brokerName
> 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
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.12.0
>
>
> 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)
