[ROCKETMQ-14]invoke callback shoule be invoked in an executor rather than in current thread. #2
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.
For success callback, processResponseCommand will execute invoke callback in a saparate executor rather than the time thread.
But for timeout problem , the timeout callback will be invoked directly in timer thread/netty selector thread.
If the user put some time-cost task when timeout, the other timeout callback will be blocked to schedule.
JIRA issue: https://issues.apache.org/jira/browse/ROCKETMQ-14