On 22 August 2011 06:28, Lionel Cons <span dir="ltr"><<a href="mailto:lionel.cons@cern.ch">lionel.cons@cern.ch</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Matthias Radestock writes:<br>
> Yes. I think you'll find that currently there are *two* message-ids in<br>
> the MESSAGE frame - the original and Rabbit's. I will file a bug to get<br>
> that fixed.<br></div></blockquote><div><br>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?<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
According to the<br></div>
STOMP 1.1 spec, only the first one (the user supplied one) should be<br>
taken into account. Hence the buggy behavior.<br></blockquote><div><br>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.<br>
<br>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 frame.<br>
<br>Cheers,<br> Tony<br><br></div></div>