activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-5705) originBrokerURL incorrectly set in advisory messages
Date Wed, 17 Jun 2015 15:43:00 GMT


Timothy Bish commented on AMQ-5705:

Wouldn't bother me, I just haven't had time to look at this one other than to see it and agree
that it makes sense that the value should probably match the connector.

> originBrokerURL incorrectly set in advisory messages
> ----------------------------------------------------
>                 Key: AMQ-5705
>                 URL:
>             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

View raw message