[jira] [Comment Edited] (SLING-6257) Sling IDE: Debugging: Thread interrupted for every uncaught exception

["Konrad Windszus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650060#comment-15650060 ] 

Konrad Windszus edited comment on SLING-6257 at 11/9/16 7:45 AM:
-----------------------------------------------------------------

This seems to happen even when doing a manual remote debugging connection (Standard Socket Attach) to Sling. So rather an Eclipse issue indeed. Seems that since Eclipse Neon this is be default enabled in Preferences -> Java -> Debug -> Suspend on uncaught exceptions.
For me the exceptions happen in all {{ThreadExpiringThreadPool}} threads with the exception {{RuntimeException}} with message "Kill old thread".


was (Author: kwin):
This seems to happen even when doing a manual remote debugging connection (Standard Socket Attach) to Sling. So rather an Eclipse issue indeed. Seems that since Eclipse Neon this is be default enabled in Preferences -> Java -> Debug -> Suspend on uncaught exceptions.
For me the exceptions happen in the {{sling-oak-observation}} threads.

> Sling IDE: Debugging: Thread interrupted for every uncaught exception
> ---------------------------------------------------------------------
>
>                 Key: SLING-6257
>                 URL: https://issues.apache.org/jira/browse/SLING-6257
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.1.0
>            Reporter: Konrad Windszus
>
> When I debug a local Sling server with the Sling IDE every uncaught exception leads to a suspension of the affected thread (in Eclipse Neon). That is the case even though no breakpoints are set in Eclipse (neither Exception breakpoints, nor class nor method breakpoints).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)