fix async invoke timeout is not accurate

[liyiwen3]

What is the purpose of the change

It is a bug that invokeAsync's timeout have not been handled accurately

Brief changelog

fix async invoke timeout is not accurate

[xiangwangcheng]

1. The scanResponseTable() method is invoked periodically(every one second), it could be late for one second for one particular reponseFuture to be scanned, in the worst case. So
   (rep.getBeginTimestamp() + rep.getTimeoutMillis() + 1000) <= System.currentTimeMillis()
   does mean something.

2. Could you please change the destination branch to devleop?

[liyiwen3]

1. The scanResponseTable() method is invoked periodically(every one second), it could be late for one second for one particular reponseFuture to be scanned, in the worst case. So
   (rep.getBeginTimestamp() + rep.getTimeoutMillis() + 1000) <= System.currentTimeMillis()
   does mean something.
2. Could you please change the destination branch to devleop?

Yes,of course，done

[liyiwen3]

Yes of course，I have changed the destination branch to devleop.

…

------------------&nbsp;原始邮件&nbsp;------------------ 发件人:&nbsp;"程向往"<notifications@github.com&gt;; 发送时间:&nbsp;2019年12月11日(星期三) 上午9:48 收件人:&nbsp;"apache/rocketmq"<rocketmq@noreply.github.com&gt;; 抄送:&nbsp;"915071628"<915071628@qq.com&gt;;"Author"<author@noreply.github.com&gt;; 主题:&nbsp;Re: [apache/rocketmq] fix async invoke timeout is not accurate (#1632) The scanResponseTable() method is invoked periodically(every one second), it could be late for one second for one particular reponseFuture to be scanned, in the worst case. So (rep.getBeginTimestamp() + rep.getTimeoutMillis() + 1000) <= System.currentTimeMillis() does mean something. Could you please change the destination branch to devleop? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.