Hi,
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
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

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 4 | next ›
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedFeb 7, '12 at 3:48a
activeFeb 10, '12 at 4:10p
posts4
users3
websiterabbitmq.com
irc#rabbitmq

People

Translate

site design / logo © 2022 Grokbase