Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-6261

ThreadExpiringThreadPool is relying on uncaught exceptions to kill threads

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Commons Threads 3.2.6
    • Fix Version/s: Commons Threads 3.2.10
    • Component/s: Commons
    • Labels:
      None

      Description

      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.

        Attachments

        1. SLING-6261-v01.patch
          65 kB
          Konrad Windszus

          Issue Links

            Activity

              People

              • Assignee:
                kwin Konrad Windszus
                Reporter:
                kwin Konrad Windszus
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: