I suppose this is a phenomenon when many tasks / tasks / runnables are executed by the executor service, which is supported by a thread pool with unknown internal queue mechanisms.
In such cases, there may be no way to predict which task is performed in which of the combined flows and particular attention should be paid to the relationship between the flows, ownership, ..
In a sense, task execution jumps from stream to stream. This is not strictly necessary; it is possible to realize affinity for streams, but it is often difficult to avoid, so you need to be careful.
I found out about this from googling for some time. Therefore, I do this community wiki.
source
share