A 1.5.1 client should be able to interact with a 2.1.0 broker. I don't know why there would be a difference in the size of the messages.
To be clear, the new encoding applies to AMQP messages which you don't appear to be using. Can you work up a simple, reproducible test-case to demonstrate the issue you're seeing? Justin On Thu, Jun 22, 2017 at 7:33 AM, hcrobison <[email protected]> wrote: > We have been using Artemis 1.5.1. Recently we upgrade the server to 2.1.0. > While it can communicate with 2.1.0 client successfully, it does not seem > to > work properly with 1.5.1 client. > > We are passing messages in protobuf format. The end result is the receiving > end can no longer deserialize the protobuf messages due to the message body > length problem. (com.google.protobuf.InvalidProtocolBufferException: While > parsing a protocol message, the input ended unexpectedly in the middle of a > field. This could mean either than the input has been truncated or that an > embedded message misreported its own length.) > > Our investigation shows that the message sent and received have a length > difference of 4 bytes. What is causing this? Could the new message encoding > has anything to do with this? Can a 2.1.0 server work with 1.5.1 client? > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Artemis-2-1-0-compatibility-with-1-5-x-tp4727741.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
