[rabbitmq-discuss] rabbitmq-c TTL setting not working for me - please help

Kim Tran ktran0003 at gmail.com
Tue Jun 17 17:59:26 BST 2014

Thanks for the hints.  I didn't have the basic.qos to receive one at a 
time. That's likely the reason.

So what would happen if I got all the messages straight away but slowly 
process them:  the queue would get bigger and bigger over time? and 
eventually crash with some socket error?


On 6/17/2014 9:39 AM, Simon MacMullen wrote:
> On 17/06/2014 5:33PM, Kim Tran wrote:
>> And I still got all the messages. None of them was dropped.
> Hang on. You originally said:
>> Then every time I consume a message, I sleep for 5 secs just to delay
>> the consuming rate.
> That would mean the broker sent you all the messages straight away, 
> but your app delayed reading them off the socket. The queue can't 
> expire messages when they are out for delivery.
> So if you want a slow consumer, set basic.qos to a low value (e.g. 1), 
> that way the broker will only send you one message at a time as you 
> acknowledge them (you are using acks, right?)
> Then you should see the messages expire.
> Cheers, Simon

More information about the rabbitmq-discuss mailing list