-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(XServiceProvider): fix ebean framework race condition #11378
fix(XServiceProvider): fix ebean framework race condition #11378
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Fixes race condition when GMS recieves a request during startup causing required initialization of ebean framework to fail.
4d45209
to
ec704b9
Compare
@@ -73,6 +73,17 @@ public void onApplicationEvent(@Nonnull ContextRefreshedEvent event) { | |||
event); | |||
String schemaRegistryType = provider.getKafka().getSchemaRegistry().getType(); | |||
if (ROOT_WEB_APPLICATION_CONTEXT_ID.equals(event.getApplicationContext().getId())) { | |||
|
|||
// Handle race condition, if ebean code is executed while waiting/bootstrapping (i.e. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the required fix.
While updating to the latest executor code in actions, a GMS startup race condition is triggered by incomplete
initialization of the ebean framework during integration/smoke-tests.
This PR fixes the race condition by loading the class prior to starting the wait/bootstrap process during GMS startup. This allows AuthenticationFilter to handle requests which require interaction with SQL via the ebean library as the application is loading.
Notes:
In production environments running kubernetes the pod would not be expected to receive traffic before the health check is healthy and would avoid this condition.
Checklist