<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 25/05/12 16:42, Simon Thorogood wrote:
<blockquote cite="mid:COL116-W381487BDAA00A802BE5228D4010@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
Thanks Tim - had missed the BasicAck. <br>
<br>
It looks like when I remove basicQos and BasicAck calls that the
QueueingBasicConsumer works fine but keeps reading from the
Rabbit queue into the internal buffer queue indefinitely (I have
set up a test case where the consumer struggles to keep up with
the loader). <br>
<br>
Would you recommend using DefaultBasicConsumer in this case? or
createing a custom Queueing consumer?<br>
<br>
Basically, I am keen to use BasicQos when we can, but would
also like to limit de-queuing of unprocessed messages in non
'ack'' scenarios.<br>
<br>
</div>
</blockquote>
<br>
In this case, it sounds like a custom consumer would serve you
better, as you'd have more fine grained control. Perhaps one of the
developers more experienced with the client(s) will chime in here
and confirm whether or not this is something that can be 'twiddled'
with the DefaultBasicConsumer however.<br>
<br>
Cheers,<br>
Tim<br>
</body>
</html>