that has been the experience in activemq. see: http://activemq.apache.org/failover-transport-reference.html
the number of attempts and the delay between retry attempts can be different for the initial connection and "re" connection. On Fri, 30 Jun 2017 at 22:12 Alan Conway <[email protected]> wrote: > This is for when we get to defining a general reconnect strategy, not > for immediate action. Satellite's reconnect issue has made me realise > this: > > Need to distinguish "connection retry" and "reconnect", may need > different behaviour: > > 1. *retry*: initial connection attempt fails, try again. > 2. *reconnect*: established connection breaks, re-establish. > > Important differences: > > 1. may involve security, misconfiguration or other permanent errors > that require application intervention. > 2. is a network failure or server fail-over, more likely to be > recoverable by automatic re-connect. > > 1. no state to be recover on retry, since there was never a connection. > 2. may need to re-establish sessions/links, re-send messages, and > let application rebuild state. > > Cheers, > Alan. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
