Fetch the extension registry again when delegate command handler not found #2184
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.
Background
Our extension's BI shows that there are some
no delegateCommandHandler
errors. It's hard to stably reproduce but looking into the code, looks that we have some issues under the concurrent scenarios.For example, when a command starts to find its delegator before it's added via
public synchronized void added(IExtension[] extensions)
.This case can be easily reproduced in debug mode:
public synchronized void added(IExtension[] extensions)
https://github.com/spring-projects/spring-petclinic/blob/main/src/main/java/org/springframework/samples/petclinic/PetClinicApplication.java
candidates
is empty after filtering), since the breakpoint postpone the handler registration into the cache.Signed-off-by: Sheng Chen [email protected]