Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of rob.j.godfrey@gmail.com
 designates 209.85.216.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1409099599208-7612615.post@n2.nabble.com>
References: 
 <CALt_PUbkySVtkCyLEO4nWK=9hRu-Sht8gTqQ-N4jqxTpxuv9BA@mail.gmail.com>
	<CAFitrpRMwGRW4hKjSMBu8ume5k2-RuRqTnBVg5J0_Y2+n7exCQ@mail.gmail.com>
	<1408777758772-7612411.post@n2.nabble.com>
	<CACsaS94Cy7DLDNi_GdvFC74EShhNyq-wyvv3o7+8D5hLG8pLuA@mail.gmail.com>
	<CA+5CJJBfMHXGLQF0JPbZ=5g+TBwMh3cD57rQzxFOwN6oc51jow@mail.gmail.com>
	<CACsaS94OzLmdPn90=7_qUShGyEfJT5YafL6cm7ZHw9hNQnDyKQ@mail.gmail.com>
	<CA+5CJJAyXfWiDr1fAb+6CtFrZ626vxdks8d=DzHRJVK4cBewQw@mail.gmail.com>
	<CACsaS95tB68jLq27kG=7mu7DneAkGGEjyFd+duHB+LG5CGme9Q@mail.gmail.com>
	<CA+5CJJDaA7vysQV95jqy-fTzw233h=hKbf-iRy0fjknpPmqqPQ@mail.gmail.com>
	<CACsaS957n3h88UXWPQMk4QKg=+b-ZU-+aEyy+KCwiwYpOZcfVA@mail.gmail.com>
	<1409099599208-7612615.post@n2.nabble.com>
Date: Wed, 27 Aug 2014 09:51:35 +0200
Message-ID: 
 <CACsaS94nJhj3waBVxw45nweNVfuM3-=f_PKwY5vXJPZZqXHYkg@mail.gmail.com>
Subject: Re: 1 Queue with 2 Consumers - turn off pre-fetching?
From: Rob Godfrey <rob.j.godfrey@gmail.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2c7e46ff8be050197b0ea

--001a11c2c7e46ff8be050197b0ea
Content-Type: text/plain; charset=UTF-8

On 27 August 2014 02:33, xiaodan.wang <xiaodan.wang@salesforce.com> wrote:

> Hi Rob, just verified with 0.32/trunk client and the v0.16 broker that we
> currently use. It is indeed doing prefetching at a per session level once I
> started the client with AMQP 0-91. Thanks so much for the suggestion!


Great!


> The
> only issue I encountered is that getJMSDestination on the message returns
> an
> instance of AMQTopic instead of javax.jms.Queue object, which was
> straightforward to work around.


Can you give me an example of the sort of address that you set the replyTo
to - I'll try to look into this and fix it before the 0.30 release goes out


> Did not encounter any other issues between
> 0.32 client/0.16 broker so far, *fingers-crossed*.
>
> Long term, we would definitely be interested in updating the broker to test
> out the multiple queue per consumer feature you are adding to trunk
> considering our options with AMQP 0-10 is non-existent at the moment.
>
> Couple of quick questions:
>
> 1) Did session-level prefetching get dropped as part of changes to the
> protocol from AMQP 0-91 -> AMQP 0-10?
>
>
Yes - it's a change at the underlying protocol level.  If you are
interested in all the gory details, the 0-9-1 specification is here:

http://www.amqp.org/specification/0-9-1/amqp-org-download

and the 0-10 specification is here

http://www.amqp.org/specification/0-10/amqp-org-download

In 0-9-1 flow control is enforced through the basic.qos method which allows
you to set a prefetch size (in terms of either bytes or messages).  In 0-10
flow control is enforced through the message.flow command which is on a per
subscription basis.


> 2) Is there any plans to drop support on the broker for versions below AMQP
> 0-10?
>
>
Absolutely not!  We have a large number of users using 0-8 / 0-9 / 0-9-1.
 The aim for the Java Broker is to support every publicly released version
of AMQP and allow interoperation between these versions as much as
possible.  The 0.30 broker release provides some enhancements both to 0-9-1
functionality and message conversions between 0-9-1 and the other AMQP
protocols.

Hope this helps,
Rob


> Thanks!
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612615.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

--001a11c2c7e46ff8be050197b0ea--