Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 63172 invoked from network); 24 Jun 2009 16:24:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jun 2009 16:24:26 -0000 Received: (qmail 41226 invoked by uid 500); 24 Jun 2009 16:24:37 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 41155 invoked by uid 500); 24 Jun 2009 16:24:36 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 41145 invoked by uid 99); 24 Jun 2009 16:24:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 16:24:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 16:24:26 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MJVGX-0002vo-RL for users@activemq.apache.org; Wed, 24 Jun 2009 09:24:05 -0700 Message-ID: <24187651.post@talk.nabble.com> Date: Wed, 24 Jun 2009 09:24:05 -0700 (PDT) From: shaldar To: users@activemq.apache.org Subject: Re: activemq-cpp client heartbeat and reconnect with broker? In-Reply-To: <5eda8340906230805l7c3df6c8ia7c309df5f9c1004@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: shaltrade@gmail.com References: <24157918.post@talk.nabble.com> <5eda8340906230805l7c3df6c8ia7c309df5f9c1004@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org 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 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.