No - that sounds like a bug to me. I wonder what the exception is that terminates the JVM?
James On 3/24/06, claudem <[EMAIL PROTECTED]> wrote: > > Yes, I had set the property maxReconnectAttempts to "0". As I described, it > works perfectly when starting the receiver before running the broker. It > waits as expected until the broker is available and connects when it is up. > > But if I later shutdown the broker, the connection breaks and the failover > code does not get back into a "waiting for connection" state. It just exits > the main loop in SimpleTaskRunner.runTask/FailoverTransprt.iterate and > stops. > > This is in the snapshot of March 23rd, and was also in M4. > > Is this a normal behavior? > > -- > View this message in context: > http://www.nabble.com/Failover-failure--t1338117.html#a3582606 > Sent from the ActiveMQ - User forum at Nabble.com. > > -- James ------- http://radio.weblogs.com/0112098/
