IGNITE-26345 Wrap ExceptionInInitializerError that happens in contructor of IgniteImpl when launched without JVM options "--add-opens=..."#7606
Open
JAkutenshi wants to merge 3 commits intoapache:mainfrom
Conversation
…ed as well as corresponding tests
…f the node start future
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
JIRA Ticket: IGNITE-26345
The goal
The main goal of the PR is to add error handlers on Ignite server node start. Error handlers in case like the title says should detect
ExceptionInInitializerErrorwithIllegalAccessExceptionsituations and wrap up it with Ignite exception with proper message to a user.The reason
We should improve our UX on node startup process in case of errors too.
The solution
IgniteServerImpl#syncmethod that handles exceptions from future likeIgniteServerImpl#startAsyncand there new handlers were added. Also new tests are implemented to check all error cases and a node startup.