[rabbitmq-discuss] STOMP & message-id
tonygarnockjones+rabbitmq at gmail.com
Mon Aug 22 12:58:27 BST 2011
On 22 August 2011 06:28, Lionel Cons <lionel.cons at cern.ch> wrote:
> Matthias Radestock writes:
> > Yes. I think you'll find that currently there are *two* message-ids in
> > the MESSAGE frame - the original and Rabbit's. I will file a bug to get
> > that fixed.
Isn't the user-supplied message-id sent in the MESSAGE as "amqp-message-id"?
In which case there really is only one "message-id" header in the MESSAGE?
> According to the
> STOMP 1.1 spec, only the first one (the user supplied one) should be
> taken into account. Hence the buggy behavior.
STOMP mentions "message-id" for MESSAGE and ACK and NACK only. It doesn't
say anything about SEND. For compatibility with the spec, the client code
should take the "message-id" from the MESSAGE and use that in any related
ACK or NACK. Don't use the "message-id" from the SEND, in other words, since
that's a RabbitMQ (and presumably also ActiveMQ etc) extension.
I'm not sure this is a bug. It's certainly something that'd be difficult to
change, because of the way STOMP 1.1 is defined and the way RabbitMQ wants
to use the message ID field. In particular, there's no real way to let
people use their own user-supplied message-id values in an ACK or NACK
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss