Perhaps I'm just approaching this the wrong way

I'm very grateful for Dejan's input on the thread http://activemq.2283324.n4.nabble.com/broker-config-if-destination-may-be-down-td3086163.html However I feel like perhaps I'm hitting this issue because of some fundamental problem with my approach. What I am trying to do is actually easy to desc

Re: broker config if destination may be down

Setting the timeout on the failover transport does indeed cause that initial connection to abort, which allows the broker to start up and enqueue bridged messages. This is what I wanted. However, I don't see any indication that the failover transport ever tries again. Using a url like the follo

Re: broker config if destination may be down

It seems like there may be a JIRA open on this (my concern about the broker hanging on startup if it cannot connect). https://issues.apache.org/jira/browse/AMQ-2114 I'd still like to know how other people handle this situation, even if it requires a heroic coding intervention. -- View this mes

Re: broker config if destination may be down

I was using the failover transport to supply multiple URIs, but I didn't realize how configurable it was. The various parameters used to configure how many reconnect attempts are made and the delay between those attempts are very helpful. The remaining question I have, though, it what is the bro

broker config if destination may be down

Hi folks, for the purposes of this question I am using activemq 5.3.1, non-persistent I would like to use the BrokerService in the normal way as a bridge between a local queue and a remote destination. The trick is that the remote destination may or may not be up at the time the BrokerService st