You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "vongosling (JIRA)" <ji...@apache.org> on 2016/12/30 03:37:58 UTC
[jira] [Resolved] (ROCKETMQ-14) Remoting invoke callback shoule be
invoked in an executor rather than in current thread.
[ https://issues.apache.org/jira/browse/ROCKETMQ-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vongosling resolved ROCKETMQ-14.
--------------------------------
Resolution: Fixed
Fix Version/s: 4.0.0-incubating
> 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
> Fix For: 4.0.0-incubating
>
>
> 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)