Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26748903.post@talk.nabble.com>
Date: Fri, 11 Dec 2009 10:09:48 -0800 (PST)
From: magellings <mark.gellings@qg.com>
To: dev@activemq.apache.org
Subject: Re: Apache NMS 1.2.0 RC1 now ready for download.
In-Reply-To: <1260549910.27208.10.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <1259712277.21082.21.camel@localhost>
 <26747457.post@talk.nabble.com> <1260549910.27208.10.camel@localhost>


So when assigning a delegate (e.g. OnMessage) to the Listener event on the
message consumer, the framework can't pull for another message after the
scope of the delegate ends?  Is this how the java implementation behaves? 
This isn't a big deal, we already were defaulting to doing pulls manually
with MessageConsumer.Receive if prefetch is set to zero.  I guess just in my
head I expected it to do it automatically even with the listener event
assigned.

http://activemq.apache.org/what-is-the-prefetch-limit-for.html 

"Specifying a prefetch limit of zero means the consumer will poll for more
messages, one at a time, instead of the message being pushed to the
consumer."

-Mark


Timothy Bish wrote:
> 
> On Fri, 2009-12-11 at 08:38 -0800, magellings wrote:
>> Hey Tim.  Could you explain this a bit more?  How come this isn't
>> possible. 
>> Seems like it should be.  Thanks :-)
>> 
>> Quad.NMS.Integration.Test.PrefetchZeroPullTest.Should_be_able_to_set_prefetch_to_zero_and_nms_activemq_enables_pull_mode
>> : Apache.NMS.NMSException : Cannot set Asynchronous Listener on a
>> Consumer
>> with a zero Prefetch size
> 
> With prefetch set to zero there is never going to be any messages
> delivered from the broker.  The perfetch zero setting basically turns
> your client into a pull consumer, each time you call
> IMessageConsumer.Receive a MessagePull command it sent to the Broker, if
> a message is available then one is delivered to the client.  With an
> asynchronous consumer there is nothing to initiate the MessagePull from
> the broker, so you'd never receive a message.
> 
> Regards
> Tim.
> 
>> 
>> 
>> Timothy Bish wrote:
>> > 
>> >                       ***** ANNOUNCEMENT *****
>> > 
>> > The Apache NMS 1.2.0 Release Candidate 1 is now available at the
>> > following location:
>> > 
>> > http://people.apache.org/~tabish/nms-1.2.0-RC1
>> > 
>> > The following projects are included:
>> > 
>> > Apache.NMS
>> > Apache.NMS.ActiveMQ
>> > Apache.NMS.EMS
>> > Apache.NMS.MSMQ
>> > Apache.NMS.WCF
>> > 
>> > There are release binaries and debug binaries (with PDBs) provided. 
>> The
>> > binary ZIP files include pre-built assemblies for all of the platforms
>> > that are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5,
>> > etc).  Not all projects support all platforms.  Please note that in
>> > order to use the Apache.NMS.EMS project files, you will need to provide
>> > your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party
>> > application.
>> > 
>> > Please report any issues or problems you have with these files.
>> > 
>> > Regards
>> > Tim Bish
>> > 
>> > 
>> > 
>> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Apache-NMS-1.2.0-RC1-now-ready-for-download.-tp26601401p26748903.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.