Handling SecurityException Security manager does not allow for static UncaughtExceptionHandler modification #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I am Diego Ocampo from Atlassian.
Statsig server init. setting Thread (static) DefaultUncaughtExceptionHandler is causing issues. The issues come from the fact that an uncaught exception that is completely unrelated to Statsig can end up shutting down Statsig background jobs.
Also, the MainThreadExceptionHandler is re-throwing the exception, which shouldnt be done as documented in:
https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.html#setDefaultUncaughtExceptionHandler-java.lang.Thread.UncaughtExceptionHandler-
By re-throwing, the exception is then handled by ThreadGroup, which ends up calling Thread.UncaughtExceptionHandler in an infinite loop, eventually killing the thread.
In this PR I am adding a graceful exception handling for security permissions so we can initialise the application and restrict Statsig from setting this top level handler, which is problematic.
#41