[
https://issues.apache.org/jira/browse/AMQ-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-5705:
-----------------------------
Assignee: Gary Tully
Regression: Unit Test Broken
this patch breaks org.apache.activemq.network.FailoverStaticNetworkTest
the PublishedAddressPolicy is now applying to the vm connector and the usage of
broker name with A_B (an underscore it) fails to be converted into a valid url,
blowing up with an exception. Our vm urls very loose, I think
PublishedAddressPolicy needs to be a little more aware of the vm scheme.
Working on a fix.
> 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)
