Yes, I would like failover transport to try reconnecting until the broker becomes available, BUT I would like it not to block! The failover transport does NOT block on later calls even if there is no connection to the broker, so why should it block on startup if the broker is down? I do not want to configure maxReconnectAttempts since I want the transport to keep trying, forever.
An example is when you configure jmsBridgeConnectors with a jmsQueueConnector using a connection factory with a failover transport. If the remote broker is not available, the local ActiveMQ instance will never finish starting up! This cannot be what you intend?!
I would expect the failover transport to start, and keep trying to connect to the remote broker.