Fix AwaitingNonWebApplicationListener await with parent context #15971
+672
−105
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.
Description
AwaitingNonWebApplicationListener should only enter the await state for the
root, non-web ApplicationContext.
When a parent–child context hierarchy is present, the listener must not await
during child context shutdown.
This PR ensures the listener behaves correctly with multiple non-web
application contexts and adds a focused regression test to cover this scenario.
Changes
Prevent awaiting logic from being triggered by child ApplicationContext
Add unit test for non-web parent–child context lifecycle
Testing
Added testMultipleContextNonWebApplication
Tests pass locally
Fixes #13722
please review it sir when you get time @AlbumenJ @RainYuY