Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 31760 invoked from network); 4 Nov 2009 21:48:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Nov 2009 21:48:08 -0000 Received: (qmail 61376 invoked by uid 500); 4 Nov 2009 20:01:28 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 61326 invoked by uid 500); 4 Nov 2009 20:01:28 -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 61316 invoked by uid 99); 4 Nov 2009 20:01:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Nov 2009 20:01:28 +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, 04 Nov 2009 20:01:19 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1N5m2M-0002DF-O9 for users@activemq.apache.org; Wed, 04 Nov 2009 12:00:58 -0800 Message-ID: <26203654.post@talk.nabble.com> Date: Wed, 4 Nov 2009 12:00:58 -0800 (PST) From: bpmuser To: users@activemq.apache.org Subject: Re: ActiveMq-Cpp soConnectTimeout not working In-Reply-To: <1257364018.3621.62.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: brian.mckinnon@nrc.ca References: <26200045.post@talk.nabble.com> <1257364018.3621.62.camel@localhost> X-Virus-Checked: Checked by ClamAV on apache.org Timothy Bish wrote: > > On Wed, 2009-11-04 at 08:50 -0800, bpmuser wrote: > The failover transport is going to keep trying to reconnect here even if > the soConnectTimeout causes the attempt to connect to fail. Have you > tried without the failover transport in the mix to see if > soConnectTimeout is working? > > tcp://127.0.0.1:61616?soConnectTimeout=1 > > If you are looking for a way to have the connection fail when using the > Failover transport then you'd probably want to set the > maxReconnectAttempts value on the Failover transport as follows. > > failover:(tcp://127.0.0.1:61616?soConnectTimeout=1)?maxReconnectAttempts=50 > > Regards > Tim. > > Removing failover worked, but adding maxReconnectAttemps to the failover put me into a lock again. I started using failover since my program was disconnecting after a minute of inactivity. Is there a way to check the connection status and restore lost connections without the failover? Or is there a way to stop the disconnect after a minute of inactivity? Cheers, Brian! -- View this message in context: http://old.nabble.com/ActiveMq-Cpp-soConnectTimeout-not-working-tp26200045p26203654.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.