On 10 February 2017 at 15:30, Justin Ross <[email protected]> wrote:
> http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core- > transport-v1.0-os.html#type-connection-error > > """ > connection-forced: > An operator intervened to close the connection for some reason. The > client could retry at some later date. > """ > > Do we interpret this to mean that clients should use their normal reconnect > behavior? > > To my mind, yes - If you get connection forced the client should use it's existing configuration (perhaps modified with extra information that it has previously received from the server about failover hosts - I'll write that up soon :-) ). > Should it be a matter of configuration? If so, what should the default be? > > I don't think that I would consider this case to be any different to simply having the connection terminate due to a network error. If the operator/server wants you to connect to a different server, it should send a redirect not a forced. > Zooming out, would it make sense to eventually introduce in AMQP an > explicit "go away, don't reconnect" variant of connection error? > What would the use case be? What would the client do in this case (go hide in a corner / delete itself from the hard disk?). Potentially we could augment the error with a minimum reconnect delay or something... but other than that I think forced (reconnect according to existing policy) and redirect (you should go somewhere else)... cover all the use cases I can think of. -- Rob
