JDK-8119105 : Still cannot rely on Thread.setDefaultUncaughtExceptionHandler() to work with JavaFX App Thread.
  • Type: Bug
  • Component: javafx
  • Sub-Component: application-lifecycle
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-05-22
  • Updated: 2015-06-17
  • Resolved: 2013-06-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Fixed
Related Reports
Relates :  
JDK-8095154 - javafx.animation.Animation#impl_finished swallows exceptions
Description
Since bug RT-15332 is fixed I was testing to make sure my application's uncaught exception handler was working properly and I noticed that the only way to have the JavaFX application thread make use of it is to set it specifically using Thread.currentThread().setUncaughtExceptionHandler().

My application already makes use of Thread.setDefaultUncaughtExceptionHandler() to make sure any new threads deal with exceptions in a consistent manner so it would be ideal if the JavaFX thread worked like this as well. 

It looks like this happens because JavaFX already sets its own uncaught exception handler which means the thread never delegates handling to its ThreadGroup which would make use of the "default" uncaught exception handler. Plus  I believe that the specific JavaFX exception handler is very similar to ThreadGroup's handling when no outside handlers are set...
Comments
Has anyone come up with an alternative, work-around to this problem?
03-09-2013
Indeed, QuantumToolkit sets its own uncaught exception handler on startup. It was missed during the fix for RT-15332 and should be removed.
06-06-2013