Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 87023 invoked from network); 21 Oct 2009 19:02:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Oct 2009 19:02:07 -0000 Received: (qmail 89216 invoked by uid 500); 21 Oct 2009 19:02:06 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 89189 invoked by uid 500); 21 Oct 2009 19:02:06 -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 89179 invoked by uid 99); 21 Oct 2009 19:02:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Oct 2009 19:02:06 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.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, 21 Oct 2009 19:02:03 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1N0gRK-0007Gu-Vd for users@activemq.apache.org; Wed, 21 Oct 2009 12:01:42 -0700 Message-ID: <25998296.post@talk.nabble.com> Date: Wed, 21 Oct 2009 12:01:42 -0700 (PDT) From: Drizzt321 To: users@activemq.apache.org Subject: Re: Strategies for purging internal consumer queue In-Reply-To: <51DDB7F0-5EFA-4284-9553-80F73C105707@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: drizzt321@gmail.com References: <2A357C54-3FD8-411B-8930-CFA31885CA3B@geoffreyarnold.com> <3a73c17c0910160328gef4a65aqfba1573c98cd32ab@mail.gmail.com> <51DDB7F0-5EFA-4284-9553-80F73C105707@gmail.com> I think that would be specifying jms.prefetchPolicy.queuePrefetch=0 as part of your connection string. This turns off the Consumer prefetch queue that you seem to be talking about. It can impact performance though. See http://activemq.apache.org/what-is-the-prefetch-limit-for.html Geoffrey Arnold-2 wrote: > > Thanks Gary. Our Cucumber tests are really integration tests, so it > would require a restart of the VM running the embedded broker. > > Is there anyway to disable the internal queue? > > On Oct 16, 2009, at 6:28 AM, Gary Tully wrote: > >> I guess it is typical to use a new session per test unless it is the >> session >> behavior that is under test? >> >> 2009/10/15 Geoffrey Arnold >> >>> Hi All, >>> >>> We are successfully using JMX to purge our queues in between our >>> Cucumber-based test scenarios, however this does not clear the >>> session's >>> internal consumer queue. This can cause messages which have been >>> delivered >>> to the consumer's session but not yet consumed by the listener >>> (perhaps >>> because of an initial delivery failure) to be redelivered in >>> subsequent test >>> scenarios. >>> >>> What strategies are you using to purge (or completely disable) the >>> internal >>> consumer queue? >>> >>> Thanks, >>> Geoff. >>> >> >> >> >> -- >> http://blog.garytully.com >> >> Open Source Integration >> http://fusesource.com > > > -- View this message in context: http://www.nabble.com/Strategies-for-purging-internal-consumer-queue-tp25915202p25998296.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.