On Thu, 2011-11-03 at 07:15 -0700, Ishitori wrote: > I experience the same problem using NMS with ActiveMQ 5.5.0 > > I've tried syntaxis: > failover:(tcp://localhost:61616)?startupMaxReconnectAttempts=1&initialReconnectDelay=1 >
Try adding transport. to the options, in NMS all options applied to the transport layer must have that prefix. > AND > > failover://(tcp://localhost:61616)?startupMaxReconnectAttempts=1&initialReconnectDelay=1 > > And it doesn't make any difference. From the client Log I can see that it > still tries to reconnect to tcp://localhost:61616/ while doubling timeout: > 10ms, 20ms, 40ms, 80ms etc... until reaches 30000ms. > > What can I do to fix the problem? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/failover-startupMaxReconnectAttempts-doesn-t-do-anything-tp3735372p3986011.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
