Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com
 designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1353045855631-4659431.post@n4.nabble.com>
References: <1352993211594-4659398.post@n4.nabble.com>
	<CAH+vQmMhbEQz3gZr8rSjyFhamJ623+tRe3bFCgF3Tc9gbLF_sQ@mail.gmail.com>
	<1353045855631-4659431.post@n4.nabble.com>
Date: Fri, 16 Nov 2012 11:26:55 +0000
Message-ID: 
 <CAH+vQmOCf2Pev5NyQUvhJOQyKs+=UE8nJdBXimJ+Ny0Zs66K6g@mail.gmail.com>
Subject: Re: jms.prefetchPolicy.queuePrefetch=1 means 2 outstanding messages?
From: Gary Tully <gary.tully@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=e89a8fb201128edcfb04ce9b0b46

--e89a8fb201128edcfb04ce9b0b46
Content-Type: text/plain; charset=ISO-8859-1

you still need to tune the prefetch. the prefetch extension is used when a
message is delivered but not acked, such that the broker and dispatch
another message, the idea being that there will always be prefetch num
messages pending. It also allows a transaction batch to exceed the prefetch
value.
So with prefetch=1, one message is dispatched, and when the broker gets a
delivered ack, it used the prefetch extension to deliver another. With
usePrefetchExtension false, it won't dispatch another message till the
original is acked.


On 16 November 2012 06:04, himanshu_s83 <himanshu_s83@yahoo.co.in> wrote:

> Ok. Sure, will try that. So I assume that with usePrefetchExtension=false,
> it
> doesn't matter whats the prefetch size. Correct?
>
> With Prefetch Size 0 we initially saw messages getting consumed faster but
> after a while, consumption rate became dead slow and queue size kept on
> increasing to a very high value, even after increasing consumers. So we
> reverted to earlier value of 1.
>
> We are using 5.0 version of ActiveMQ and consumers are created in a
> threadpool with each consumer thread having a dedicated session. Our
> threaded model is straightforward:
>
> while(1) {
> consumer.receive() //threads block here for new message
> processMessgae() //message get processed here
> acknowledge() //message get acknowledged
> }
>
> In addition to above, we are catching exceptions and calling
> "session.recover()" appropriately.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/jms-prefetchPolicy-queuePrefetch-1-means-2-outstanding-messages-tp4659398p4659431.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
http://redhat.com
http://blog.garytully.com

--e89a8fb201128edcfb04ce9b0b46--