[AMQCPP-358] FailoverTransport can peg CPU when connection attempts exceeds max and its waiting to be closed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.5
• Fix Version/s: 3.2.6, 3.3.0
• Component/s: Transports
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 29/Mar/11 23:02
• Updated: 30/Mar/11 19:27
• Resolved: 30/Mar/11 19:27

Description

While waiting for its parent to close it the FailoverTransport can peg the CPU in the case where a limit is set on reconnect attempts.