Continuation is used for database actions that are a continuation of some previously executed actions
Fresh is used for database actions that are scheduled/queued for the first time.
WithConnection is used for database actions that already have a JDBC connection associated.
Create an AsyncExecutor with a thread pool suitable for blocking I/O.
Create an AsyncExecutor with a thread pool suitable for blocking I/O. New threads are created as daemon threads.
A prefix to use for the names of the created threads.
The number of core threads in the pool.
The maximum number of threads in the pool.
The size of the job queue, 0 for direct hand-off or -1 for unlimited size.
The maximum number of configured connections for the connection pool. The underlying ThreadPoolExecutor will not pick up any more work when all connections are in use. It will resume as soon as a connection is released again to the pool Default is Integer.MAX_VALUE which is only ever a good choice when not using connection pooling
when the number of threads is greater than the core, this is the maximum time that excess idle threads will wait for new tasks before terminating.
If set to true, register an MXBean that provides insight into the current queue and thread pool workload.
Create an AsyncExecutor with a thread pool suitable for blocking I/O.
Create an AsyncExecutor with a thread pool suitable for blocking I/O. New threads are created as daemon threads.
A prefix to use for the names of the created threads.
The number of threads in the pool.
The size of the job queue, 0 for direct hand-off or -1 for unlimited size.