Timothy Bish created AMQ-5231:
---------------------------------
Summary: Failover Transport timeout option causes connection
failures in some cases where it shouldn't
Key: AMQ-5231
URL: https://issues.apache.org/jira/browse/AMQ-5231
Project: ActiveMQ
Issue Type: Improvement
Components: Transport
Affects Versions: 5.10.0, 5.9.1, 5.9.0, 5.8.0
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Minor
Fix For: 5.11.0
Originally added in AMQ-2061 the timeout option is used to cause a send of
Message that's gone out async to fail if the connection doesn't come back in
some amount of time.
The problem is that the option is currently applied to everything that goes
through FailoverTransport oneway() and this can cause a Connection start where
the broker is not up to fail regardless of the maxReconnectAttempts or
startupMaxReconnectAttempts value configured for the transport.
We need to refine the timeout logic to only apply to Message instances and not
to other commands like ConnectionInfo so that a Connection start honors the
normal failover transport reconnect configuration logic.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
