I did some quick testing and it looks like the first version it breaks is 5.12.0. It seemed to work ok in 5.11.3.
5.12.0 was a big release though with over 200 issues so will still need to narrow it down more. In the meantime I would say if the TCP transport works then go with that, I doubt you will notice much if any real performance impact. On Thu, May 31, 2018 at 3:30 PM, codingismy11to7 <ste...@codemettle.com> wrote: > The current workaround we've been testing is to change to the TCP transport > from the VM transport on the code that runs inside the broker process > (where > we want to guarantee that some queues or topics are always are being dealt > with as long as ActiveMQ is running). That seems like it would be a pretty > big inefficiency, but so far it looks to have eliminated the null bodies. > If > it's recommended that the VM transport should never be used, then we can > deal with that. I'm not going to rewrite all of our unit tests to not use > VM > transport, but the odds of any of them failing because of this seems low. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev- > f2368404.html >
