Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <613046171.1234816259738.JavaMail.jira@brutus>
Date: Mon, 16 Feb 2009 12:30:59 -0800 (PST)
From: "Uwe Kubosch (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Issue Comment Edited: (AMQ-2114) Failover transport should
 not hang on startup if it cannot connect
In-Reply-To: <1914299144.1234567619344.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49699#action_49699 ] 

donv edited comment on AMQ-2114 at 2/16/09 12:29 PM:
------------------------------------------------------------

Yes, I would like failover transport to try reconnecting until the broker becomes available, BUT I would like it not to block!  The failover transport does NOT block on later calls even if there is no connection to the broker, so why should it block on startup if the broker is down?  I do not want to configure maxReconnectAttempts since I want the transport to keep trying, forever.

An example is when you configure jmsBridgeConnectors with a jmsQueueConnector using a connection factory with a failover transport.  If the remote broker is not available, the local ActiveMQ instance will never finish starting up!  This cannot be what you intend?!

I would expect the failover transport to start, and keep trying to connect to the remote broker.

      was (Author: donv):
    Yes, I would like failover transport to try reconnecting until the broker becomes available, BUT I would like it not to block!  The failover transport does NOT block on later calls even if there is no connection to the broker, so why should it block on startup if the broker is down?  I do not want to configure maxReconnectAttempts since I want the transport to keep trying, forever.

An example is when you configure jmsBridgeConnectors with a jmsQueueConnector using a connection factory with a failover transport.  If the remote broker is not available, the local ActiveMQ instance will never finish starting up!  This cannot be what you intend?!

  
> Failover transport should not hang on startup if it cannot connect
> ------------------------------------------------------------------
>
>                 Key: AMQ-2114
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2114
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.2.0
>         Environment: Sun Java 1.6.0_12
> Fedora Linux 10
> ActiveMQ 5.2.0
>            Reporter: Uwe Kubosch
>            Priority: Critical
>
> When connecting with a failover transport, like the DEFAULT_BROKER_URL, the transport hangs on connection.start() if it cannot connect to the remote broker.  It should return normally.
> This only happens on startup.  Later disconnects behave nicely.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.