sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (SLING-6261) ThreadExpiringThreadPool is relying on uncaught exceptions to kill threads
Date Wed, 12 Apr 2017 08:43:41 GMT

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

Konrad Windszus reassigned SLING-6261:
--------------------------------------

    Assignee: Konrad Windszus

> ThreadExpiringThreadPool is relying on uncaught exceptions to kill threads
> --------------------------------------------------------------------------
>
>                 Key: SLING-6261
>                 URL: https://issues.apache.org/jira/browse/SLING-6261
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Threads 3.2.6
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Commons Threads 3.2.8
>
>         Attachments: SLING-6261-v01.patch
>
>
> In {{o.a.s.commons.threads.impl.ThreadExpiringThreadPool}} a {{RuntimeException}} with
message "Kill old thread" is used in {{checkMaxThreadAge(final Thread thread)}}. This leads
by default to a suspension of the thread when debugging with Eclipse (as since Neon JDT will
suspend the thread on all uncaught exceptions). More information is available in http://stackoverflow.com/questions/6290470/eclipse-debugger-always-blocks-on-threadpoolexecutor-without-any-obvious-excepti.
There should be a different mechanism to kill the thread than an uncaught exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message