[
https://issues.apache.org/jira/browse/AMQNET-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-300.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Patch applied, thanks.
> NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover
> Transport
> -------------------------------------------------------------------------------
>
> Key: AMQNET-300
> URL: https://issues.apache.org/jira/browse/AMQNET-300
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: Stomp
> Affects Versions: 1.4.0
> Reporter: Andreas Ländle
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.5.0
>
> Attachments: startupMaxReconnectAttempts.patch
>
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
