[
https://issues.apache.org/activemq/browse/AMQ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-2114.
--------------------------------
Resolution: Fixed
Hi Uwe,
this is exactly what failover transport should do (try reconnecting until
broker becomes available). If you want to limit the number of retries try using
the maxReconnectAttempts option, such as
failover:(tcp://localhost:61616)?maxReconnectAttempts=3
> 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.
