Workaround an issue where the JNDIInitializer would be called several times #563
Conversation
This file contains 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
Workaround an issue where the JNDIInitializer would be called several times, making it wait for an unavailable JNDI data source multiple rounds instead of just one. I can't figure out why JNDIDataSourceAutoConfiguration would be instantiated several times when JNDIInitializer fails, so added a static flag to JNDIInitializer to avoid waiting for unavailable databases again and again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Workaround an issue where the JNDIInitializer would be called several times, making it wait for an unavailable JNDI data source multiple rounds instead of just one.
I can't figure out why JNDIDataSourceAutoConfiguration would be instantiated several times when JNDIInitializer fails, so added a static flag to JNDIInitializer to avoid waiting for unavailable databases again and again.
Also Refactor the simple JNDI configuration to auto and plain config classes