[rabbitmq-discuss] STOMP & expiration

Toby Corkindale toby.corkindale at strategicdata.com.au
Thu Oct 20 01:10:19 BST 2011

On 22/08/11 19:13, Matthias Radestock wrote:
> Lionel,
> On 22/08/11 10:07, Lionel Cons wrote:
>> It seems that RabbitMQ does not handle the "expires" STOMP header.
>> Although this is not in the STOMP spec, it's commonly used in
>> JMS-compliant brokers to handle expiration.
>> Is there any plan to support message expiration via STOMP?
> Is that header set on a per-message basis? If so then Rabbit won't
> support that any time soon.
> With AMQP we support a per-queue setting that controls message expiry.
> See http://www.rabbitmq.com/extensions.html#queue-ttl.

I'm using the STOMP plugin for RabbitMQ, which is auto-vivifying the 
queues for me; is there an easy way to tell it to also pass the 
x-message-ttl header along?

(I'm happy to use the per-queue setting since the per-message stuff 
isn't implemented)


More information about the rabbitmq-discuss mailing list