activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alistair Young <alistair.yo...@uhi.ac.uk>
Subject Re: failover startupMaxReconnectAttempts doesn't do anything
Date Thu, 11 Aug 2011 17:48:50 GMT
I decided to use a background thread instead and let it block on that instead. Using 5.2.0
but it won't let me set options when using failover.

> use failover:(urls)failoveroptions
tried to set startupMaxReconnectAttempts but it complains it's not a valid option

-------------------
Alistair Young
Àrd Innleadair air Bathair-bog
UHI@Sabhal Mòr Ostaig

On 11 Aug 2011, at 17:08, Gary Tully wrote:

> use failover:(urls)failoveroptions
> 
> so:
> 
> failover:(tcp://localhost:61617)?maxReconnectAttempts=1
> 
> What version you using?
> 
> On 11 August 2011 10:42, Alistair Young <alistair.young@uhi.ac.uk> wrote:
>> found this:
>> 
>> http://comments.gmane.org/gmane.comp.java.activemq.user/30654
>> 
>> which suggested this:
>> 
>> failover://(tcp://localhost:61617)?startupMaxReconnectAttempts=1&initialReconnectDelay=10&maxReconnectAttempts=2&maxReconnectDelay=10
>> 
>> which causes this:
>> 
>> javax.jms.JMSException: Could not create Transport. Reason: java.lang.IllegalArgumentException:
Invalid connect parameters: {startupMaxReconnectAttempts=1}
>> 
>> Alistair
>> 
>> 
>> --
>> mov eax,1
>> mov ebx,0
>> int 80h
>> 
>> 
>> 
>> 
>> On 11 Aug 2011, at 10:33, Alistair Young wrote:
>> 
>>> If I try to connect to a dead broker:
>>> 
>>> failover:tcp://localhost:61617
>>> 
>>> it blocks forever on:
>>> 
>>> ActiveMQConnectionFactory connectionFactory::setClientID
>>> 
>>> if I force it to not block:
>>> 
>>> failover:tcp://localhost:61617?startupMaxReconnectAttempts=1&initialReconnectDelay=10
>>> 
>>> it still blocks.
>>> 
>>> Am I missing something?
>>> 
>>> thanks,
>>> 
>>> Alistair
>>> 
>>> --
>>> mov eax,1
>>> mov ebx,0
>>> int 80h
>>> 
>>> 
>>> 
>>> 
>> 
>> 
> 
> 
> 
> -- 
> http://fusesource.com
> http://blog.garytully.com


Mime
View raw message