[
https://issues.apache.org/jira/browse/ROCKETMQ-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780033#comment-15780033
]
ASF GitHub Bot commented on ROCKETMQ-14:
----------------------------------------
Github user zhouxinyu commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/2
Hi,
This PR has been merged, but next time please use JIRA issue
name(`ROCKETMQ-14`) as branch name instead of `master`. Please refer to
[here](http://rocketmq.apache.org/docs/pull-request/) for more details.
Thanks.
> Remoting invoke callback shoule be invoked in an executor rather than in
> current thread.
> -----------------------------------------------------------------------------------------
>
> Key: ROCKETMQ-14
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-14
> Project: Apache RocketMQ
> Issue Type: Improvement
> Reporter: Jaskey Lam
> Assignee: vongosling
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
