]
Paul Ferraro commented on WFLY-6415:
------------------------------------
Since the pool size is fixed, the term "max-threads" is confusing, since the
number of threads is constant. I suggest we rename this to "threads" or
"size".
Deprecate
org.jboss.as.clustering.infinispan.subsystem.ScheduledThreadPoolResourceDefinition#keepAliveTime
since it has no valid meaning
----------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-6415
URL:
https://issues.jboss.org/browse/WFLY-6415
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
{code}
* <p>While this class inherits from {@link ThreadPoolExecutor}, a few
* of the inherited tuning methods are not useful for it. In
* particular, because it acts as a fixed-sized pool using
* {@code corePoolSize} threads and an unbounded queue, adjustments
* to {@code maximumPoolSize} have no useful effect. Additionally, it
* is almost never a good idea to set {@code corePoolSize} to zero or
* use {@code allowCoreThreadTimeOut} because this may leave the pool
* without threads to handle tasks once they become eligible to run.
{code}