[
https://issues.apache.org/activemq/browse/AMQ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61087#action_61087
]
Alec Bickerton commented on AMQ-2114:
-------------------------------------
As I see it.
If you use
vm:(broker:(tcp://localhost:61616,network:static:tcp://remotehost:61616)) then
you're explicitly not using the failoverprotocol. IMHO, this should be
re-opened and properly fixed.
> 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
> Assignee: Rob Davies
> Priority: Critical
> Fix For: 5.3.2
>
>
> 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.
