History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: AMQ-1089
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Olaf Brandt
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

Warning when using multicast discoveryUri

Created: 05/Dec/06 07:04 AM   Updated: 26/Feb/07 10:23 AM
Component/s: None
Affects Version/s: 4.0.1, 4.0.2
Fix Version/s: 5.0.0, 4.1.1

Time Tracking:
Not Specified

Environment: reproduced on Windows XP Pro and SuSE Linux Enterprise 9.1

Patch Info: Patch Available


 Description  « Hide
When using a transportconnector with a multicast discoveryagent a warning is shown.

config: <transportConnector name="default" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>

WARN MulticastDiscoveryAgent -brokerName not set

When the transportconnector is started the MulticastDiscoveryAgent is created if it does not exist,
but the brokerName for this MulticastDiscoveryAgent is not set by the transportconnector.

See the code and the suggested modification to prevent this warning:

org.apache.activemq.broker.TransportConnector.java

<snip>
public void start() throws Exception {
getServer().start();
DiscoveryAgent da = getDiscoveryAgent();
if( da!=null ) {
da.registerService(getConnectUri().toString());
//suggested modification start
if(da.getBrokerName() == null || da.getBrokerName().length == 0) { da.setBrokerName(this.getBroker().getBrokerName()); }
//suggested modification end
da.start();
}
this.statusDector.start();
log.info("Connector "getName()" Started");
}
<snap>



 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
Jonas Lim - 06/Dec/06 02:28 AM
i believe this has already been resolved in the 4.2 trunk (r464216)

Jonas Lim - 06/Dec/06 03:02 AM
btw, this issue has also been resolved in the 4.1.0 release