I agree on the versions - first match the client and broker version and see if that helps. Running with the latest too is a good idea to make sure this isn't a bug that was already fixed.
With that said, one workaround that may help here - disable the cache feature in the protocol (it helps by reducing the size of messages when the same information is sent many times, such as producer ID). The setting is called "cacheEnabled". See the following page for more information: http://activemq.apache.org/configuring-wire-formats.html -- View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-Message-Processing-Failed-tp4698776p4698829.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
