You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/01/23 15:23:00 UTC

[jira] [Resolved] (SLING-7433) Improve logging in case ThreadLocalCleaner does not work

     [ https://issues.apache.org/jira/browse/SLING-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved SLING-7433.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Commons Threads 3.2.14

Fixed in https://github.com/apache/sling-org-apache-sling-commons-threads/commit/1ffb9d9c12637e790151ad499cfb2c5738e9dbdd.

> Improve logging in case ThreadLocalCleaner does not work
> --------------------------------------------------------
>
>                 Key: SLING-7433
>                 URL: https://issues.apache.org/jira/browse/SLING-7433
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Threads 3.2.10
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Commons Threads 3.2.14
>
>
> Currently {{ThreadLocalCleaner}} relies on exceptions in case anything in it does not work as expected. Those exceptions are most probably not correctly caught and logged by the Oracle implementation calling {{ThreadPoolExecutor.beforeExecute(...)}} and {{ThreadPoolExecutor.afterExecute(...)}}. Therefore all exceptions should be caught and logged there explicitly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)