activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AFinnell <and...@activesol.net>
Subject Re: Failover transport hangs on startup if it cannot connect to a broker
Date Thu, 19 Feb 2009 15:42:48 GMT

Check out http://activemq.apache.org/failover-transport-reference.html

If it is attempting to establish a connection it will block. 

With the timeouts and such you might be able to get around start() blocking
and do your own queuing of messages because if there isn't a valid
connection the send() will throw after a timeout.


donV wrote:
> 
> Hi all!
> 
> The failover transport should return normally on connection.start() even
> if it cannot connect to a remote broker on startup, right?
> 
> In all cases I am trying, it blocks on startup, preventing
> initialization of the rest of the ActiveMQ components.
> 
> I have filed a Jira issue on this: AMQ-2114
> 
> Anyone, please feel free to clarify the usage of the failover transport
> in case I am missing something.  What I expect from the failover
> transport is robustness regarding remote broker connection failures.
> 
> -- 
> With kind regards,
> Uwe Kubosch
> Datek Wireless
> Norway
> http://datek.no/
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Failover-transport-hangs-on-startup-if-it-cannot-connect-to-a-broker-tp22006976p22103198.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message