[jira] [Work logged] (AMQNET-331) Failover protocol fails to reconnect if client started while broker is not running.

["Jim Gomes (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQNET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()} ]

Jim Gomes logged work on AMQNET-331:
------------------------------------

                Author: Jim Gomes
            Created on: 18/Jun/11 00:16
            Start Date: 18/Jun/11 00:16
    Worklog Time Spent: 4h 

Issue Time Tracking
-------------------

            Worklog Id:     (was: 11335)
            Time Spent: 4h
    Remaining Estimate: 0h  (was: 4h)

> Failover protocol fails to reconnect if client started while broker is not running.
> -----------------------------------------------------------------------------------
>
>                 Key: AMQNET-331
>                 URL: https://issues.apache.org/jira/browse/AMQNET-331
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ, Stomp
>    Affects Versions: 1.5.1
>         Environment: Windows 7 64-bit, .NET 4.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>              Labels: failover, mutex
>             Fix For: 1.5.2
>
>   Original Estimate: 4h
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> If a client using the failover protocol is started prior to the broker being started, the reconnect strategy will never connect the client.  This is reproducible if the transport timeout is used to avoid blocking on initial connect.
> For some clients, it is required that they run in a disconnected mode, and can't be stopped from starting or running if the broker is offline.  However, once the broker comes online, they will connect to it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira