Fix: the interface-level timeout and retry configurations become invalid after the caller application is restarted #15784
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.
Details: By moving the subscription logic after initializing referenceConfigurationListener in the dynamic configuration
Addresses: #15783
What is the purpose of the change?
What's the problem
In Dubbo 3.2.11 and all latest Dubbo 3 versions, the interface-level timeout and retry configurations become invalid after the caller application is restarted
Root cause
The investigation into why the referenceConfigurationListener was null points to a potential timing issue in the RegistryDirectory class's subscribe method: providers are being subscribed to before the referenceConfigurationListener is initialized.
How to fix
I solve this problem by placing the referenceConfigurationListener initialization logic before the call to super.subscribe(url).
Checklist