We have seen a number of messages fail due to an errant \n at the beginning of the frame. This causes the frame command to be invalid, though the message is legitimate.
We believe there is a race condition occurring where AMQ is adding the additional \n after the \0 at the end of the previous frame, but that the is_ready? check at the end of a frame read is just missing it.
We have seen a number of messages fail due to an errant \n at the beginning of the frame. This causes the frame command to be invalid, though the message is legitimate.
We believe there is a race condition occurring where AMQ is adding the additional \n after the \0 at the end of the previous frame, but that the is_ready? check at the end of a frame read is just missing it.