s?
> Inmediate fail in case both B brokers are down?
>
> Regards
> Eduardo Corral
>
> delphz escribió:
>> OK, it was my mistake, i set a boolean to late...
>>
>> Now, I have the following configuration :
>> failover://(tcp://B1:61616,tcp://B2:62626)?maxReconnectAt
have : javax.jms.JMSException: Connection refused.
Have you got an idea ?
delphz wrote:
>
> I set the maxReconnectAttempts to 1 and it is trying to reconnect
> endlessly. And it can't connect to the B servers, even if they are up.
>
>
> Eduardo Corral wrote:
>>
>>
ameter, but they are trying to reconnect endlessly...
>
> http://activemq.apache.org/failover-transport-reference.html
>
> With failover, you may also configure how long between retries and how
> many of them.
>
> Best regards,
> Eduardo Corral
>
> delphz escrib
Hello,
I have some servers A1, A2, AN, ... that send messages on a queue on servers
B1 ans B2. I configured my A servers to connect with the following URI :
failover:(tcp://B1:61616,tcpB2:62626). But when activemq is stopped on both
B1 and B2, my servers A wait a long time before deciding that B1
I think that I have the same problem.
I have a client on a server A that sends JMS messages on a activemq broker
on a server B. The messages are send on the queue "queue.reporting". There
is a persistence database on my server B. When I look at the messages, I see
that the container is queue://qu
