Hello.!
I think that I've found an explanation of this behavior that is
probably not a bug.
Our code that fails because of the unreadable content is called by an
ExchangeSentEvent handler. After debugging this code, setting a
breakpoint on the StreamCache reset method, I see that the stream is
re
Hello.
We've some kind of random behavior on routes that use stream caching,
with the default configuration. All our routes are executed using
blueprints in Karaf. The same error happens on old Camel 2.x on Fuse
and Camel 3.21.x on Karaf 4.x.
In some cases the previous body is the result of a JAX
