David Url

I also got bitten by this error after upgrading from activemq 5.15.15 to 5.16.4, And brave-instrumentation-jms from 512.7 to 5.13.7 (via spring-cloud-dependencies). Our workaround is to call `message.reset()` in our...

Got bitten again... This time in a component that uses camel to receive jms messages. But in this case camel maps ByteMessage to byte[] and sends it to a bean....

There is a similiar issue #66 where errors are not printed when running javac in forked mode.

My workaround is to catch the exception and rethrow its cause if it fits. So from now on, I will be living in fear of an update breaking this behavior....

> The code generated by 4.21.x happens to be backwards compatible with 3.20.x and (I think) 3.19.x. The eventual criteria we are aiming for will not guarantee that code generated...