Any idea on this problem? What i wrote about the 10 seconds made me look for
configuration parameters that are 1 ms by default, and i found
maxInactivityDurationInitalDelay. I've tried changing it in the consumer
uri:
failover://(tcp://host1:61616?wireFormat.maxInactivityDurationInitalDelay=9
Thanks for your help. Unfortunately, TRACE level doesnt show anything
relevant. However, i've been trying different things and it seems this
problem happens only after the first 10 seconds of the consumer's activity.
I mean, if i make all the process i explained really fast (i never did
before my f
Thanks for your help. Unfortunately, TRACE level doesnt show anything
relevant. However, i've been trying different things and it seems this
problem happens only after the first 10 seconds of the consumer's activity.
I mean, if i make all the process i explained really fast (i never did
before my f
you will get more information with TRACE level logging for FailoverTransport
There are a bunch of retry config options but the default is to
continue to retry for ever.
If you want to see what it does/can do, the source is at:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java
