Why does inflight message not get rerouted by failover on loadbalance

[catlinit]

I have a message which is stuck as inflight due to the fact that the activemq endpoint has been taken down. However, we set up the route with a loadbalance and alternate location e.g.

Should the inflight message not be rerouted to activemq2 when the original uri is not available?

thanks.

[davsclaus]

Which is the original url?

You most likely need to enable sync send, to trigger failover using the Camel load balancer, as sync send will cause an exception, which is what the Camel load balancer triggers upon

http://activemq.apache.org/async-sends.html

Alternatively the AMQ broker connection url support failover as well so you do not need to use the Camel load balancer for sending a msg to a network of AMQ brokers

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

See the failover transport guide as well here

http://fusesource.com/docs/broker/5.5/connectivity_guide/FuseConnectivityFailover.html

[catlinit]

Many thanks davsclaus, using the AMQ failover option was the way to go.

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

Edited by: ilsteam on Nov 4, 2011 1:47 PM