[rabbitmq-discuss] Counting messages dropped because of expired TTL

• Previous message: [rabbitmq-discuss] When using rabbitmq-jms javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card
• Next message: [rabbitmq-discuss] Counting messages dropped because of expired TTL
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi there, 

We recently ran into a situation where we have more message than we can 
process, so I want to temporarily drop certain unimportant messages. This 
will be using a per-message TTL. I was wondering whether it was possible to 
see how many messages are actually dropped because their TTL has expired by 
the time they end up at the front of the queue. Is this information tracked 
and obtainable by Rabbit, or would I have to resort to a DLX-approach and 
process those dead messages manually?

Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131210/2d50f28c/attachment.html>

• Previous message: [rabbitmq-discuss] When using rabbitmq-jms javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card
• Next message: [rabbitmq-discuss] Counting messages dropped because of expired TTL
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]