I'm trying to realize a stress test in a Camel project that receives a key to decrypt some query parameters. However, when I add multiple vusers, the sequence of threads seems to lose the order.
The thread 7 enter in the middle of the sequence of thread 4, is there anyway to control this? In these cases where the sequence is broken, I can't decrypt data cause in the thread I have other key to open.
I'm using direct: in my route, I've tried to use seda with no concurrentConsumers and the process become to slow, utilizando concurrentConsumers parameter the same error.