Scratch that. Your real question is, "Why does does a Socket.connect() on
Windows wait the full timeout period when attempting to connect to a host
that's down, while on Linux it fails almost immediately." You can probably
find that out using the debugger; set a breakpoint client at
FailoverTrans
It sounds like you're seeing exponential backoff disabled in Linux; if
exponential backoff is in use then the delay will increase quickly from
10ms up to whatever max is set (see lines 1145-1151 of
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.11.1/org/apache/ac
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 (on
