[ROCKETMQ-14] Remoting invoke callback shoule be invoked in an executor rather than in current thread.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.0.0-incubating
• Assignee: Von Gosling
• Reporter: Jaskey Lam
• Created: 26/Dec/16 04:36
• Updated: 04/Jan/17 02:19
• Resolved: 30/Dec/16 03:37

Description

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.

Issue Links

• links to: GitHub Pull Request #2
• links to: GitHub Pull Request #19