Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 6410 invoked from network); 15 Apr 2009 00:21:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Apr 2009 00:21:34 -0000 Received: (qmail 2893 invoked by uid 500); 15 Apr 2009 00:21:33 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 2819 invoked by uid 500); 15 Apr 2009 00:21:33 -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 2809 invoked by uid 99); 15 Apr 2009 00:21:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 00:21:33 +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, 15 Apr 2009 00:21:24 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LtssB-0007er-Cv for users@activemq.apache.org; Tue, 14 Apr 2009 17:21:03 -0700 Message-ID: <23050409.post@talk.nabble.com> Date: Tue, 14 Apr 2009 17:21:03 -0700 (PDT) From: yesnid To: users@activemq.apache.org Subject: Re: Send Timeout Version 5.3? In-Reply-To: <23050391.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: nsimi@pelco.com References: <23050022.post@talk.nabble.com> <23050391.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Hello, Thank you for the fast reply, I need this to be transport agnostic, as I would like to use this in conjunction with the VM transport, and I really am only interested in controlling send timeouts right now. thank you! mdasari wrote: > > Hi, > > I don't know about 5.3 roadmap, but regarding your "timeout" issue. > > Would "soTimeout" and "connectionTimeout" (from TCP transport options) > work for your use case? > > cheers > - mdasari > > > yesnid wrote: >> >> Hello All, >> >> According to the following page: >> >> http://activemq.apache.org/failover-transport-reference.html >> >> the timeout transport option is availible in ActiveMQ Version 5.3? is >> this correct? If so when is 5.3 due for release? If not what am I doing >> wrong with the following connection string such that I cannot connect to >> my broker when I specify the time out? >> >> "failover:(tcp://localhost:61616)?randomize=true&maxReconnectAttempts=1&timeout=3000" >> >> Thank you! >> > > -- View this message in context: http://www.nabble.com/Send-Timeout-Version-5.3--tp23050022p23050409.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.