Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 46561 invoked from network); 22 Jun 2006 15:09:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jun 2006 15:09:49 -0000 Received: (qmail 50608 invoked by uid 500); 22 Jun 2006 15:09:49 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 50583 invoked by uid 500); 22 Jun 2006 15:09:49 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 50566 invoked by uid 99); 22 Jun 2006 15:09:48 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 08:09:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 08:09:46 -0700 Received: by ug-out-1314.google.com with SMTP id m3so571582uge for ; Thu, 22 Jun 2006 08:09:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=sT2ObnRUVR1pQ7rSm8pT1kOYDy1jVaHgNktBHCI3AiPVboHq2gvMv1xn2iw6MyrfLLLYCziDEQb3LRIFfquyL5TLLCdUpAoorWjp75kc9ouFOdb5ZQUi5AbXDQ7u4GIlbB5t0LM3Yw+1OkQDf8YOGXnJmfjjClZs91ZJ+CWkWcI= Received: by 10.66.219.11 with SMTP id r11mr1161546ugg; Thu, 22 Jun 2006 08:09:24 -0700 (PDT) Received: by 10.66.237.18 with HTTP; Thu, 22 Jun 2006 08:09:24 -0700 (PDT) Message-ID: Date: Thu, 22 Jun 2006 11:09:24 -0400 From: "Hiram Chirino" Sender: chirino@gmail.com To: activemq-users@geronimo.apache.org Subject: Re: consumer.dispatchAsync defaults to false In-Reply-To: <4982777.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4982777.post@talk.nabble.com> X-Google-Sender-Auth: 863ec631950943df X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Great question. Open a JIRA issue to report the bug here: http://issues.apache.org/activemq/browse/AMQ We will either fix the documentation or the code. Regards, Hiram On 6/21/06, yaussy wrote: > > Seems like there was a change between 4.0-RC3 and incubator-4.0 with regards > to the default value for the destination option "consumer.dispatchAsync". > According to the web documentation for destination options, as well as > behavior in RC3, the default is true. However, it looks like incubator-4.0 > defaults to false. I have to explicitly give the > consumer.dispatchAsync=true for a destination option, in order to get async > dispatch in the Broker. > > Is this a code bug, or documentation bug? > -- > View this message in context: http://www.nabble.com/consumer.dispatchAsync-defaults-to-false-t1826678.html#a4982777 > Sent from the ActiveMQ - User forum at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com