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 2016/11/09 07:54:59 UTC

[jira] [Created] (SLING-6261) ThreadExpiringThreadPool is relying on uncaught exceptions to kill threads

Konrad Windszus created SLING-6261:
--------------------------------------

             Summary: 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


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.4#6332)