https://issues.apache.org/bugzilla/show_bug.cgi?id=56492
Bug ID: 56492
Summary: Avoid eclipse debugger pausing on uncaught exceptions
when tomcat renews its threads
Product: Tomcat 8
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: slaur...@apache.org
Currently when tomcat is run with eclipse debugger and a Context is reloaded,
each thread that exits (because of the feature to renew threads) triggers a
breakpoint in eclipse if its "Suspend execution on uncaught exceptions" is
enabled (which is the default).
This has been reported to eclipse :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=384073 which closed it without
change in eclipse.
This also has a high number of votes on
http://stackoverflow.com/questions/6290470/eclipse-debugger-always-blocks-on-threadpoolexecutor-without-any-obvious-excepti
and is deemed as quite annoying.
The attached patch fixes tomcat by not letting the exception go out of
Thread.run() and thus trigger the debugger. Instead, a custom exception is
thrown to have the Thread go out of the ThreadPool and then caught and
swallowed before Thread.run() returns.
Patch is against tomcat 8 trunk and passes checkstyle and NIO2 tests.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
