I believe it should silently reconnect if it detects that the broker went away. You may also want to see this ticket for your specific case:
https://issues.apache.org/activemq/browse/AMQCPP-246 On Wed, Jun 24, 2009 at 11:56 PM, shaldar <shaltr...@gmail.com> wrote: > > Hi Chetan - I tested with 3.0 as you suggested. I built and used the > SimpleAsyncConsumer.cpp example that comes with 3.0. It's connecting and > receiving messages from the remote broker. > > However, changing the brokerURI to failover://(tcp://207.153.194.152:61616 > ) > or failover://(tcp://207.153.194.152:61616?maxInactivityDuration=1000) > doesn't seem to have any effect when I pull off the internet connection. > > Is there a specific Exception I should be catching in the consumer when the > KeepAlives fail? There is an exception listener in the code but that > doesn't > fire when KeepAlives should be failing. > > Best - Susmit > > > Chetan Sarva-2 wrote: > > > > 3.0 now requires that you initialize the library before using it. Simply > > call: > > > > activemq::library::ActiveMQCPP::initializeLibrary(); > > > > and clean it up with: > > > > activemq::library::ActiveMQCPP::shutdownLibrary(); > > > > no other code changes are required. You can simply use a broker URI with > > failover like: > > > > failover://(tcp://localhost:61616) > > > > chetan > > > > On Wed, Jun 24, 2009 at 12:24 PM, shaldar <shaltr...@gmail.com> wrote: > > > >> > >> Thanks chetan - I am using 2.2.6 . I tried changing to 3.0 but it gave > me > >> a > >> runtime error. To save time, I changed my links back to 2.2.6. > >> > >> In any case - 2.2.6 has a bunch of code related to maxInactivityDuration > >> and > >> KeepAliveInfo in the activemq::connector::openwire::commands namespace. > >> > >> If this feature is indeed there - what is the best way to access it? I > >> have > >> been using the cms::connection which pretty much ignores extensions to > >> the > >> brokerURI. Is there a different namespace I should go to for more > >> features? > >> Any sample code will be helpful. > >> > >> Best - Susmit > >> > >> > >> Chetan Sarva-2 wrote: > >> > > >> > Which version of the library are you using? The latest version, 3.0, > >> which > >> > was released less than 2 weeks ago, supports the failover transport > for > >> > handling scenarios like this. > >> > > >> > chetan > >> > > >> > On Mon, Jun 22, 2009 at 8:22 PM, shaldar <shaltr...@gmail.com> wrote: > >> > > >> >> > >> >> Hi all - > >> >> > >> >> I wrote a publish/subscribe clients that seem to be working well with > >> the > >> >> broker. I want make the clients more reliable - particularly when the > >> >> network connection goes down. This is especially needed for the > >> >> subscriber, > >> >> which just sits on an asynchronous listener once the connection > >> starts. > >> >> > >> >> Is there anything simple I can do in my main loop that checks for the > >> >> health > >> >> of the connection to the broker? > >> >> > >> >> Also, if the connection goes down, should I just attempt to restart > >> the > >> >> connection - or - do I have to recreate new connection, session and > >> >> consumer > >> >> objects? > >> >> > >> >> Any ideas or sample codes will be very helpful. > >> >> > >> >> Best - Susmit > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > http://www.nabble.com/activemq-cpp-client-heartbeat-and-reconnect-with-broker--tp24157918p24157918.html > >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> >> > >> >> > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/activemq-cpp-client-heartbeat-and-reconnect-with-broker--tp24157918p24187651.html > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/activemq-cpp-client-heartbeat-and-reconnect-with-broker--tp24157918p24196578.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
