On 07/02/12 03:48, Mihir Mone wrote:
The really baffling fact is that only configuration 1 has this issue,
configuration 2 works fine. The only difference is a different OS at the
remote end of things in configuration 2.
Can you reproduce this problem with a smaller message, or without usingThe really baffling fact is that only configuration 1 has this issue,
configuration 2 works fine. The only difference is a different OS at the
remote end of things in configuration 2.
shovel?
Does it also happen when you receive the message with any other AMQP
client, or with the "rabbitmqadmin get" command?
Have you confirmed that the original message sent to the broker does not
already contain the defect?
-Emile
