You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2010/11/29 22:08:11 UTC
[jira] Created: (AMQNET-295) Add new startupMaxReconnectAttempts
option to the Failover Transport
Add new startupMaxReconnectAttempts option to the Failover Transport
--------------------------------------------------------------------
Key: AMQNET-295
URL: https://issues.apache.org/jira/browse/AMQNET-295
Project: ActiveMQ .Net
Issue Type: Improvement
Components: ActiveMQ
Affects Versions: 1.4.1
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Trivial
Fix For: 1.5.0
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 message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQNET-295) Add new startupMaxReconnectAttempts
option to the Failover Transport
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-295.
---------------------------------
Resolution: Fixed
Fixed in trunk.
> Add new startupMaxReconnectAttempts option to the Failover Transport
> --------------------------------------------------------------------
>
> Key: AMQNET-295
> URL: https://issues.apache.org/jira/browse/AMQNET-295
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.4.1
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.5.0
>
>
> 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 message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.