[ https://issues.apache.org/jira/browse/SLING-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-6296: ------------------------------------ Fix Version/s: Commons Threads 3.2.8 > DefaultThreadPool causes warning when minPoolSize == 0 > ------------------------------------------------------ > > Key: SLING-6296 > URL: https://issues.apache.org/jira/browse/SLING-6296 > Project: Sling > Issue Type: Bug > Components: Commons > Affects Versions: Commons Threads 3.2.6 > Reporter: Rob Ryan > Fix For: Commons Threads 3.2.8 > > > DefaultThreadPool inappropriately emits a warning when a pool has a min pool > size of 0. > A min pool size of 0 is supported by the downstream ThreadExpiringThreadPool, > and is logically useful when 'empty' is a reasonable size of a pool, e.g. > when no work is apriori expected for the pool. > The code in question is: > // Min pool size > if (this.configuration.getMinPoolSize() < 1) { > this.configuration.setMinPoolSize(1); > this.logger.warn("min-pool-size < 1 for pool \"" + this.name + > "\". Set to 1"); > } > The downstream code in ThreadExpiringThreadPool only enforces this value is > >= 0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)