score:296

Accepted answer

the posted stack trace indicates that a runtimeexception was encountered in a daemon thread. this is typically uncaught at runtime, unless the original developer caught and handled the exception.

typically, the debugger in eclipse is configured to suspend execution at the location where the exception was thrown, on all uncaught exceptions. note that the exception might be handled later, lower down in the stack frame and might not lead to the thread being terminated. this would be cause of the behavior observed.

configuring the behavior of eclipse is straightforward:
go to window > preferences > java > debug and uncheck suspend execution on uncaught exceptions.

score:2

i have noticed that this often occurs after modifying server files (jsp or java) and sts has trouble reloading the application.

this usually leads to restarting the server in order to get it to get the changes synchronized.

after introducing jrebel - it appears to have gone away. so, i would like to think it is a reproducible issue in sts when hotswapping code in debug mode.

by removing the native hotswapping, it eliminates the issue with it breaking inside the threadpoolexecutor class.

score:25

this behavior is triggered by tomcat when a webapp is reloaded. it's part of tomcat "memory leak protection" feature that (among other things) forces the renewal of its threads.

this is now fixed from versions 7.0.54 and 8.0.6 of tomcat : https://issues.apache.org/bugzilla/show_bug.cgi?id=56492

score:48

there's a more specific solution, which prevents eclipse breaking on runtimeexceptions thrown only from a given class.

  1. add a new exception breakpoint from the debugging perspective
  2. go to its properties
  3. go to filtering
  4. in "restrict to selected location(s)", click "add class"
  5. add java.util.concurrent.threadpoolexecutor
  6. untick the checkbox, meaning these will be ignored

Related Query

More Query from same tag