[GR-49807] Modify substitutions for the SecurityManager to behave the same as the JDK when 'java.security.manager' is not set. #7805
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.
Before this change the function
System#setSecurityManager
was always halting program execution with a VM error. This was inconvenient as the VM error prints an uncomprehensible error message and prevents further continuation of the program. For cases where the program is expected to throw an exception whenSystem#setSecurityManager
is called, execution on Native Image was not possible.Now,
System#setSecurityManager
throws anjava.lang.UnsupportedOperationException
by default. If the propertyjava.security.manager
is set toallow
the program will exit with code99
by printing a user-readable stack trace.After this change:
Before this PR: