I am having a problem with setDefaultUncaughtExceptionHandler(...) not working when the Java application is launched from AdvancedInstaller.
When the java application is launched from the command line, uncaught exceptions are caught and handled by the application's UncaughtExceptionHandler. When the application is launched by AdvancedInstaller the applications UncaughtExceptionHandler is not invoked even though tracing through the program shows it is set by Thread.setDefaultUncaughtExceptionHandler(...)
If I enable AdvancedInstaller's "Startup failure check" then the AdvancedInstaller dialogue box is displayed with the details of the uncaught exception.
It would seem that perhaps AdvancedInstaller is disabling or in some way preventing an existing DefaultUncaughtExceptionHandler but will insert its own if "Startup failure check" is enabled?
I'm not sure whether this behaviour has changed from previous versions? I thought our uncaught exception processing used to work but can't be sure as it always works in our eclipse development environment since we don't launch from AdvancedInstaller there.