[AMQNET-300] NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: Stomp
• Patch Info: Patch Available
• Assignee: Timothy A. Bish
• Reporter: Andreas Ländle
• Created: 29/Dec/10 10:18
• Updated: 29/Dec/10 13:35
• Resolved: 29/Dec/10 13:35

Description

Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.

This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.

This would also make sense for the STomp Failover-Transport - patch attached (shamelessly a copy of the solution of AMQNET-295).

Issue Links

• is a clone of: AMQNET-295 Add new startupMaxReconnectAttempts option to the Failover Transport