You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "fucongwang (JIRA)" <ji...@apache.org> on 2017/10/07 07:03:00 UTC

[jira] [Created] (ROCKETMQ-301) Async callback timeout

fucongwang created ROCKETMQ-301:
-----------------------------------

             Summary: 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.1.0-incubating, 4.0.0-incubating
            Reporter: fucongwang
            Assignee: vongosling
             Fix For: 4.2.0-incubating


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)