jerryk at rbcon.com
Thu Apr 4 19:51:50 BST 2013
What characterizes a pass or fail for your particular tests?
The behavior you'd expect to see is documented at:
"While consumers never see expired messages, only when expired messages
reach the head of a queue will they actually be discarded (or
dead-lettered). When setting a per-queue TTL this is not a problem, since
expired messages are always at the head of the queue. When setting
per-message TTL however, expired messages can queue up behind non-expired
ones until the latter are consumed or expired. Hence resources used by such
expired messages will not be freed, and they will be counted in queue
statistics (e.g. the number of messages in the queue)."
On Thu, Apr 4, 2013 at 10:56 AM, Derek Greer <dbgreer at gmail.com> wrote:
> I've got several tests which publish a message with a TTL of 1 millisecond
> and then attempt to pull the message off was fail intermittently. I've
> altered the tests to insert a thread sleep of 1, 3, 5 and finally 10
> seconds before the tests pass 100% of the time. This seems to be a bug.
> Are messages checked for expiration periodically, at the point a consumer
> connects and dequeues, both? It would seem the latter isn't happening.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss