[rabbitmq-discuss] STOMP & message-id
lionel.cons at cern.ch
Mon Aug 22 10:15:39 BST 2011
I've tried to send a message that contained a message-id to RabbitMQ's
STOMP interface and it got rejected with an error: Invalid message-id.
This (i.e. client supplied message-id) can happen when you shovel
messages from one broker to another.
IMHO, there are two ways for the broker to handle this:
1) ignore this header and always set a "unique" message-id, like in
the case this header is not set
2) use this header as provided by the client
If the expected behavior is 2), RabbitMQ should IMHO be liberal in
what it accepts as message-id so that messages coming from other
brokers can be shoveled easily. If there are restrictions, they should
be clearly documented.
More information about the rabbitmq-discuss