Hi Emile,

No this problem does not occur if the message is small. The payload is
basically database table rows that are being synched between two sites.
When the number of rows per payload is under 10 this error does not
occur. But once it starts getting past 15 or so I am seeing this error.
The configuration 1 which has this error is configured for 500 rows,
which configuration 2 is configured for 3000 rows. And configuration 2
works fine !!

Yes the error is present even when you receive a message through
"rabbitmqadmin get" command.

Yes, I have confirmed that the original message sent to the broker at
the remote end is OK. If you see the screenshots I have sent in the
original email, one of them is named remote-site and the other is named
local-site. They are nothing but dumps taken from the
rabbitmq_management web UI.

- Mihir
On 8/02/2012 2:37 AM, Emile Joubert wrote:
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 using

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?


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 4 | next ›
Discussion Overview
grouprabbitmq-discuss @
postedFeb 7, '12 at 3:48a
activeFeb 10, '12 at 4:10p



site design / logo © 2022 Grokbase