You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Peter Voss (JIRA)" <ji...@apache.org> on 2009/05/04 09:43:38 UTC
[jira] Commented: (AMQ-2114) Failover transport should not hang on
startup if it cannot connect
[ https://issues.apache.org/activemq/browse/AMQ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51495#action_51495 ]
Peter Voss commented on AMQ-2114:
---------------------------------
The resolution of this issue has been set to fixed. If that's really true, what's the fix version then?
> 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.