[rabbitmq-discuss] RabbitMQ manager and Idle queues

[Antoine Berry]

Hi Simon,

Thank you for the quick answer. We will upgrade !
It was in the patch note indeed, but we hadn't seen it.
About the queue ttl, we saw it too, but the problem is that it doesn't 
seem to check if there still are some messages in the queue, and no 
consumer on it (for exemple), so it will be deleted anyway. Or that's 
not the behavior we wanted, if we understood it well.

Cheers

Antoine

Le 16/04/13 15:00, Simon MacMullen a écrit :
> Hi. There was a bug introduced in 3.0.0 and fixed in 3.0.2 where 
> queues would sometimes not hibernate when idle (which is what drives 
> those "last_event" fields and the "active" flag). So the short answer 
> is "please upgrade".
>
> But you should be cautious about driving anything from those 
> "last_event" fields anyway - you're essentially looking at when the 
> queue process last woke up, and something as trivial as "rabbitmqctl 
> list_queues" will wake the queue process up.
>
> You might want to look at http://www.rabbitmq.com/ttl.html#queue-ttl 
> as an alternative.
>
> Cheers, Simon
>
> On 16/04/13 13:50, Antoine Berry wrote:
>> Hello everybody,
>>
>> We have a little problem with the rabbitMQ management plugin. Basically
>> we would want to delete the Idle queues. So to do that we send a http
>> request to the rabbitMQ management plugin REST API, to get the value of
>> the "last_event" field.
>> But we always get last_event = now, even though we haven't used the
>> queue nor the virtual host in general for a day... Plus these queues
>> don't even have any consumers, and the application is not even running.
>> And all the queues are marked as active in the web management page too.
>>
>> Here are an exemple of request, and a screen shot of the web manager
>> page, which shows a queue without any consumers but marked as active :
>>
>> HTTP/1.1 200 OK
>> Server: MochiWeb/1.1 WebMachine/1.9.0 (someone had painted it blue)
>> Date: Tue, 16 Apr 2013 09:54:44 GMT
>> Content-Type: application/json
>> Content-Length: 909
>> Cache-Control: no-cache
>>
>> {"policy":"","exclusive_consumer_tag":"","messages_ready":0,"messages_unacknowledged":0,"messages":0,"consumers":0,"active_consumers":0,"memory":44356,"backing_queue_status":{"q1":0,"q2":0,"delta""delta","undefined",0,"undefined"],"q3":0,"q4":0,"len":0,"pending_acks":0,"target_ram_count":"infinity","ram_msg_count":0,"ram_ack_count":0,"next_seq_id":66,"persistent_count":0,"avg_ingress_rate":0.0,"avg_egress_rate":0.0,"avg_ack_ingress_rate":0.0,"avg_ack_egress_rate":0.0},"messages_details":{"rate":0.0,"interval":10001924,"last_event":1366106079385},"messages_ready_details":{"rate":0.0,"interval":10001924,"last_event":1366106079385},"messages_unacknowledged_details":{"rate":0.0,"interval":10001924,"last_event":1366106079385},"consumer_details"],"name":"theQueue","vhost":"myHost","durable":true,"auto_delete":false,"arguments":{},"node":"rabbit at myServer"} 
>>
>>
>>
>> Does anybody ever had this kind of problem? We're using RabbitMQ 3.0.1,
>> with the java client.
>>
>> Thank you.
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>