When performing concurrent processing outside of a parallel stream, I have lazily used the common fork join pool to avoid creating my own executor service. Many times I have used it for blocking I/O operations which then have the ability to saturate the pool and therefore block all other attempts for other threads to use parallel streams as they were designed.
What do you think about adding a rule to warn when calling execute/submit/invoke*/newTaskFor/etc... directly on the common pool?
When performing concurrent processing outside of a parallel stream, I have lazily used the common fork join pool to avoid creating my own executor service. Many times I have used it for blocking I/O operations which then have the ability to saturate the pool and therefore block all other attempts for other threads to use parallel streams as they were designed.
What do you think about adding a rule to warn when calling
execute/submit/invoke*/newTaskFor/etc...
directly on the common pool?https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ForkJoinPool.html#commonPool--