You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Andreas Ländle (JIRA)" <ji...@apache.org> on 2010/12/29 11:21:45 UTC
[jira] Updated: (AMQNET-300) NMS.Stomp: Add new
startupMaxReconnectAttempts option to the Failover Transport
[ https://issues.apache.org/jira/browse/AMQNET-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Ländle updated AMQNET-300:
----------------------------------
Component/s: (was: ActiveMQ)
Stomp
Fix Version/s: (was: 1.5.0)
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.
was:
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.
Patch Info: [Patch Available]
Affects Version/s: (was: 1.4.1)
1.4.0
Summary: NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport (was: Add new startupMaxReconnectAttempts option to the Failover Transport)
> 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
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.