In our rpc, we use another way to circumvent the problem of different server timestamps.
The time is recorded when the runnable(in dubbo, means `ChannelEventRunnable`) is initialized: `time1`, and the time is recorded when the runable is executed: `time2`. `time2 - time1` indicates the amount of time runnable waits in the server side thread pool. If the waiting time exceeds the timeout set by the client, the response is not written to the client. [ Full content available at: https://github.com/apache/dubbo/issues/4041 ] This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For additional commands, e-mail: notifications-h...@dubbo.apache.org
