[
https://issues.apache.org/jira/browse/SLING-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7433:
---
Description: 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. (was: Currently {{ThreadLocalCleaner}}
relies on exceptions in case 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.)
> 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
>
> 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)
