[
https://issues.apache.org/jira/browse/ROCKETMQ-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vongosling closed ROCKETMQ-301.
-------------------------------
Resolution: Feedback Received
> Async callback timeout
> ----------------------
>
> Key: ROCKETMQ-301
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-301
> Project: Apache RocketMQ
> Issue Type: Improvement
> Components: rocketmq-remoting
> Affects Versions: 4.0.0-incubating, 4.1.0-incubating
> Reporter: fucongwang
> Assignee: vongosling
> Fix For: 4.2.0
>
>
> Motivation:
> I found that ResponseFuture used some tips to keep future callback
> from being called multiple and keep semaphoreAsync from being released
> multiple, I think it was not elegant, and scanResponseTable would scan the
> on-going request list, it was too heavy.
> Modification:
> * ScheduleExecutor replaces Timer, to issue per callback timeout.
> when timeout, check future is done? if not , clear responseTable item and
> invoke callback, if done, just clear responseTable item.
> * ResponseFuture add isDone method, to check if future is done.
>
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
