activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Kubosch (JIRA)" <>
Subject [jira] Commented: (AMQ-2114) Failover transport should not hang on startup if it cannot connect
Date Mon, 16 Feb 2009 20:29:04 GMT


Uwe Kubosch commented on AMQ-2114:

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

View raw message