[rabbitmq-discuss] STOMP and persistent messages to a queue destination

Jerry Kuch jerryk at vmware.com
Thu Feb 2 17:22:55 GMT 2012

Hi, Michael...

Apologies.  When I responded somewhat glibly earlier I missed the key bit
of context that you're talking about STOMP, about which I know relatively little.

The plugin creates its "/queue" queues as durable automatically, so that part
of my admonition is taken care of, and it works through the default exchange,
which is always there, so that won't be the problem...

Your messages do indeed appear to be published with persistence requested.
Are you losing some or a lot?  When is the broker restart happening?  Could it
be that the broker is bouncing before it's been able to accept responsibility 
for your message and get it safely on disk?

Looking at the STOMP adapter's web page, I see we've got what appears to be
an inert non-link where we promise to tell you about the actual semantics of
this operation:


Rabbit's publisher confirm extension, for ensuring that the broker has really
taken responsibility for a message you've published is documented here:


Are you asking for receipts when you publish?

Best regards,

----- Original Message -----
From: "Michael Justin" <michael.justin at gmx.net>
To: rabbitmq-discuss at lists.rabbitmq.com
Sent: Thursday, February 2, 2012 6:54:41 AM
Subject: [rabbitmq-discuss] STOMP and persistent messages to a queue	destination


with RabbitMQ 2.7.1 I tested persistent messages based on the STOMP 
description which says "Setting the persistent header to true has the 
effect of making the message persistent."

So the frame which sends a message to a queue has this header:


Do I also have to do something with the queue to make it persistent? 
This is not clear from the documentation - and I found that the messages 
so not survive a broker restart

Many thanks in advance
Michael Justin
habarisoft - Enterprise Messaging Software for Delphi

rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com

More information about the rabbitmq-discuss mailing list