activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <>
Subject [jira] Resolved: (AMQ-2114) Failover transport should not hang on startup if it cannot connect
Date Sun, 11 Jul 2010 16:22:56 GMT


Rob Davies resolved AMQ-2114.

    Fix Version/s: 5.3.2
                       (was: 5.4.1)
       Resolution: Won't Fix

This is working as designed - i.e. it has to block on starting a connection. If you are publishing
a message and a failure occurs - the connection would block too. To get the behaviour were
the connection doesn't block - you need to use an embedded broker with a network connection
to do store and forward. So instead of creating a connection factory with a URL of:


you could use a broker URI - e.g.


see for more details

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

View raw message