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.
Attachments
Issue Links
- is cloned by
-
AMQNET-300 NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport
-
- Resolved
-