Hi,
Yes indeed, the initialReconnectDelay doesn't seem to have effect at all,
the producer is reconnecting immediately regardless of the value specified.
Do you happen to know why?
Thanks,
Qian
Adrian Co wrote:
>
> Hi,
>
> The initialReconnectDelay is the delay for the first attempt only.
Hi,
The initialReconnectDelay is the delay for the first attempt only. Is it
reconnecting immediately on the first try?
Use the maxReconnectDelay to specify the delay for succeeding attempts.
http://activemq.apache.org/failover-transport-reference.html
Regards,
Adrian Co
Qian Su wrote:
Hi,
Hi,
Thanks for the reply. I do see retry attempts from FailoverTransport in the
stacktrace now, however the initialReconnectDelay param doesn't seem to have
effect.
I applied the following producer URL to broker and it seems that the 2
retries are attempted immediately.
failover://(tcp://local
On 29 Feb 2008, at 03:10, Qian Su wrote:
Hi,
We are using Activemq version 4.1.1, tcp transport and we'd like the
producer to retry at least once in case of connection timeout to a
broker.
The brokers are configured behind a load balancer.
Does Activemq support retries on the producer end
On 29/02/2008, Qian Su <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We are using Activemq version 4.1.1, tcp transport and we'd like the
> producer to retry at least once in case of connection timeout to a broker.
> The brokers are configured behind a load balancer.
>
> Does Activemq support retries
