fix bug lazy client share_executor is null #9701
Merged
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
|
dubbo版本 2.7.15 |
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.
What is the purpose of the change
fix bug lazy client ThreadlessExecutor.sharedExecutor is null error
发现的现象：
lazy模式的dubboreference第一次调用不会返回直到超时（实际数据已经很快返回收到）
问题点：
ThreadlessExecutor.execute函数，waiting = false，所以sharedExecutor is null 报空指针
原因分析：
lazy模式ThreadlessExecutor先创建，后Exchangers.connect导致（因为线程创建在AbstractClient的构造函数initExecutor）