[
https://issues.apache.org/activemq/browse/AMQ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49991#action_49991
]
Dejan Bosanac commented on AMQ-2114:
------------------------------------
Hi,
I just investigated this a bit further. The problem is that connection.start()
tries to send a ConnectionInfo packet to the broker to establish the
connection. When the connection is established successfully, the succeeding
start() calls will not do this, so it may appear that it behaves differently in
that case.
Anyhow, this is crucial step in establishing a connection, so it has to be done
synchronously, because all later operations (creating a sessions, consumers,
etc.) assumes the valid connection. Perhaps the issue you described with
jmsQueueConnector and failover transport should be tackled somewhere else (not
the connection.start() procedure).
> 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.
