HenrikJannsen f90c4b8f6b Use cachedThreadPool which uses SynchronousQueue instead of ArrayBlockingQueue. ... When ArrayBlockingQueue is used (as in case of using Utilities.getListeningExecutorService) the maxPoolSize has no effect. The pool creates never more threads than the core pool size. Thus we have been limited to 15 threads for message sending and connection creation. This was likely a reason why seed nodes are not accepting new connections if the pool is exhausted. Slow message send can block a thread for 1-3 minutes. Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>		2022-12-13 17:33:31 -05:00
..
src	Use cachedThreadPool which uses SynchronousQueue instead of ArrayBlockingQueue.	2022-12-13 17:33:31 -05:00