Yes, it does reconnect to the same broker. I recommend using it to ensure reliability against network outages.
I also noticed that you are running against an ActiveMQ 5.6 SNAPSHOT. Is there a reason you haven't upgraded to the shipping version? If the problem is due to a problem on the server side, someone else may not be able to replicate it. Also it shouldn't be necessary to call Acknowledge() in the message handler if you have AutoAcknowledge set. On Tue, Aug 28, 2012 at 7:58 AM, TrainTime <zzuza...@gmail.com> wrote: > I was not using the failover protocol, though I just tried it and it did > not appear to fix anything. I don't think it really applies in my situation > because there's only one broker, not many. Unless if there's just one > broker > does it just try to reconnect to the one over and over? > As for pattern, I haven't really noticed one, which has made this all the > more frustrating. The only thing that seems to be constant, is we have a > gap in data (ie. |--data----|..............[----data---]). The gap in my > testing file is probably about a minute, maybe 2 at most, and it usually > disconnects at some random time in that duration. But I've also seen it > successfully stay connected the whole time. I'm trying to > enableStatusMonitoring on the transport connector now and hopefully get > some > more useful information. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/C-Consumers-Disconnecting-tp4655632p4655721.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
