activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From MarcusSmith <marc...@hp.com>
Subject Issue with fanout multicast
Date Sat, 14 Nov 2009 18:33:47 GMT

Im using 5.3.0 on a windows XP box.

I'm using the following connection URL:
fanout:(multicast://default?maxReconnectAttempts=1)?minAckCount=1

When broker urls are discovered, i get the following notification:

Daemon Thread
[Notifier-MulticastDiscoveryAgent-listener:org.apache.activemq.transport.fanout.FanoutTransport@136102e]
(Suspended (breakpoint at line 518 in FanoutTransport))	
	FanoutTransport.add(URI[]) line: 518	
	DiscoveryTransport.onServiceAdd(DiscoveryEvent) line: 78	
	MulticastDiscoveryAgent$2.run() line: 504	
	ThreadPoolExecutor$Worker.runTask(Runnable) line: 886	
	ThreadPoolExecutor$Worker.run() line: 908	
	Thread.run() line: 619	

which is great, but at "DiscoveryTransport.onServiceAdd(DiscoveryEvent)
line: 78", which is
next.add(new URI[] {URISupport.applyParameters(uri, parameters)});

parameters is always null.  The way FanoutTransportFactory creates a
DiscoveryTransport, 
by just new'ing w/o using the DiscoveryTransportFactory prevents me from
setting any
parameters.

What i want to do is append the parameter "?connectionTimeout=1" onto the
URL at
line 78 of DiscoveryTransport.onServiceAdd, so discovered brokers that can't
be connected do
don't hold up FanoutTransport.doConnect loop 30 seconds (which is the
default timeout in 
TcpTransport) at a time.

Any thought about how to add parameters on the DiscoveryTransport when
created by the
FanoutTransportFactory would be greatly appreciated.

Thanks,

Marcus

-- 
View this message in context: http://old.nabble.com/Issue-with-fanout-multicast-tp26352574p26352574.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


Mime
View raw message