Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <16164347.10131291065013810.JavaMail.jira@thor>
Date: Mon, 29 Nov 2010 16:10:13 -0500 (EST)
From: "Timothy Bish (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQNET-295) Add new startupMaxReconnectAttempts
 option to the Failover Transport
In-Reply-To: <10479066.10051291064891917.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.