Also, what I've noticed is that maxReconnectAttempts=0 and maxReconnectAttemps=1 have the same behavior. Is it intended to be this way? I'm using ActiveMQ 5.11.1.
>From the documentation: mport9491 wrote > From version 5.6 onwards: -1 is default and means retry forever, 0 means > don't retry (only try connection once but no retry). > > All versions: If set to >0, then this is the maximum number of reconnect > attempts before an error is sent back to the client. So does this mean if your maxReconnectAttempts is either 0 or 1 then the initial/maxReconnectDelay will not take effect? -- View this message in context: http://activemq.2283324.n4.nabble.com/FailoverTransport-reconnecting-too-fast-on-Linux-compared-to-Windows-tp4699410p4699450.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
