[
https://issues.apache.org/jira/browse/SLING-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston resolved SLING-5882.
-------------------------------
Resolution: Fixed
fixed in https://svn.apache.org/repos/asf/sling/trunk@1753662
> ThreadExpiringThreadPoolTest fails 8% of time
> ---------------------------------------------
>
> Key: SLING-5882
> URL: https://issues.apache.org/jira/browse/SLING-5882
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Threads 3.2.6
> Reporter: Ian Boston
> Fix For: Commons Threads 3.2.8
>
>
> The unit tests fail 8% of the time due to a) methods not being able to
> complete in time on slower (2.53 GHz 2 core) boxes, and b) the ThreadFactory
> using an unstable method of determining if a thread is in the pool or not. It
> relies on the thread being alive, however the thread that should be dead may
> have removed itself from the pool but not yet died when the test checks.
> Increasing the thread lifetime to 90ms from 15ms and pausing for 15ms to
> ensure that threads that expired have really removed themselves from the pool
> reduces the failure rate to below 0.1%. Making that 0% would need
> introspection of the pool rather than relying on the thread being alive as a
> proxy for being in the pool.
> commit pending.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
