activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From icfantv <>
Subject Re: Connection creation timeout setting
Date Fri, 16 Jan 2009 20:46:04 GMT


Yah, I just discovered that and posted a response to myself for posterity.

Let me make sure I understand the failover transport correctly: It will, by
default, attempt to reconnect every 30 seconds indefinitely until an
ActiveMQ server is running on the default URL (assuming no additional
failover urls)?

And to answer your question, at first, I thought I didn't want the
connection thread to block, period.  But the more I think about it, if my
above understanding of the failover transport is correct, I think I like
that functionality better because it keeps me from having to handle
connection failures - at least on the code side of things.


bsnyder wrote:
> On Fri, Jan 16, 2009 at 8:27 AM, icfantv <>
> wrote:
> Just to make sure I understand what you're asking, you don't want the
> client thread that's trying to connect to the broker to block until a
> connection is completed, correct? You must be using the failover
> transport to connect because it will block and wait for the connection
> to be made based on its configuration:
> If you use the straight TCP transport without the failover transport
> the call will not block and wait:
> As far as connecting to the broker in an asynchronous manner when
> using the failover transport, such functionality does not exist
> currently.
> Bruce

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message