Hi Stephan,
I actually don't think you should fix anything in Camel, I think users
needs to be aware of race conditions that might occur when tasks are
run in parallel. Perhaps by using aggregation at the end of the
multicast. There is also `onPrepareRef` that can be used to prepare
the exchange co
Hi,
I have found a flaw in the HTTP-Session Handling I implemented some time ago:
If all the endpoints supporting HTTP-Session Handling are called in a multicast
and the scope of the session is supposed to be the exchange, this will not work
as expected.
See the following examples:
