this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613381.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
is the right approach going
forward.
By the way, what is the typical release time frame for Qpid (with
v0.32/trunk in mind)?
Cheers, Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613381
-delivered? Namely, can the message get lost if the
client dies after discarding the message but before it is re-enqueued?
Cheers, Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613337.html
Sent from the Apache
.
Cheers, Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613356.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
for each prefetched
message.
Cheers, Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613356.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
Cool beans, we did not set max message delivery attempt or enable DLQ on our
broker :)
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613363.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
0-10 is the right approach going
forward.
By the way, what is the typical release time frame for Qpid (with
v0.32/trunk in mind)?
Cheers, Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613381.html
Sent from
solved the AMQTopic/Queue issue.
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612835.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
me
know if it helps.
Awesome, the latest trunk solved the AMQTopic/Queue issue.
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612835.html
Sent from the Apache Qpid users mailing
.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612825.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e
.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612825.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional
not know what messages the client is actively working on.
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612830.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
the message
lease to be rescinded by the broker... again though we've not yet tried to
implement these more complex interaction patterns.
Hope this helps,
Rob
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching
to their nature.
I haven't requested inclusion of this change into 0.30 yet... but let me
know if it helps.
Awesome, the latest trunk solved the AMQTopic/Queue issue.
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre
this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612668.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
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
by a AMQP 0-91 client?
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612668.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
should be good - improvements have (as
far as I can remember) been around non-JMS corner cases.
Hope this helps,
Rob
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612668.html
Sent from the Apache
Hi Rob, thanks for the background info, definitely helpful!
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612674.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
for versions below AMQP
0-10?
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
versions exception when trying to
create
a
consumer using AMQP 0-9. Will get it sorted out tomorrow :)
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612411
.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612411.html
Sent from the Apache Qpid users mailing list archive at
Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612411.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612411.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands
using AMQP 0-9. Will get it sorted out tomorrow :)
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612411.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
with many
messages).
This seems to indicate that there is a separate prefetch buffer for each
consumer within the same session. Thanks in advance for any help
interpreting this behavior!
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers
-Consumers-turn-off-pre-fetching-tp6934582p7612403.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h
interpreting this behavior!
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612403.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
prefetch buffer for
each
consumer within the same session. Thanks in advance for any help
interpreting this behavior!
Cheers! Dan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612403
Hi Robbie,
I tested this fix today. It works like a charm. Thanks a lot.
Praveen
On Sun, Oct 30, 2011 at 12:02 PM, Praveen M lefthandma...@gmail.com wrote:
awesome. Thanks a lot Robbie :-)
On Sun, Oct 30, 2011 at 11:52 AM, Robbie Gemmell robbie.gemm...@gmail.com
wrote:
I have made a
I have made a change to the client on trunk that should result in it
now doing what you want when using prefetch=1 on transacted sessions
when using onMessage().
Robbie
On 28 October 2011 02:25, Robbie Gemmell robbie.gemm...@gmail.com wrote:
Ok, I havent actually tried this yet, but after
awesome. Thanks a lot Robbie :-)
On Sun, Oct 30, 2011 at 11:52 AM, Robbie Gemmell
robbie.gemm...@gmail.comwrote:
I have made a change to the client on trunk that should result in it
now doing what you want when using prefetch=1 on transacted sessions
when using onMessage().
Robbie
On 28
Hi Robbie,
I was testing against trunk, and also, I was calling commit after my
simulated processing delay, yes.
Thanks,
Praveen
On Thu, Oct 27, 2011 at 5:11 PM, Robbie Gemmell robbie.gemm...@gmail.comwrote:
Just to be clear for when I look at it...were you using trunk or 0.12
for those
Ok, I havent actually tried this yet, but after sneaking a look at the
code I am pretty sure I see a problem in the client specific to
transacted AMQP 0-10 sessions with prefetch=1 that would cause the
behaviour you are seeing. I'll look into it at the weekend. Time for
sleep, before 3am comes
Hi Jakub,
Thanks for your reply. Yes I did find the prefetch model and reran my test
and now ran into another issue.
I set the prefetch to 1 and ran the same test described in my earlier mail.
In this case the behavior I see is,
The 1st consumer gets the 1st message and works on it for a while,
35 matches
Mail list logo