* Use ExecutorService instead of event loop for Netty connection This change addresses the issue of the event loop being blocked for an extended period, improving overall performance and responsiveness. * fix log getConnectAddress * applay format * applay format * applay format * applay format * applay format * Use an independent ExecutorService * Use ScheduledExecutorService for scheduling tasks * delete unnecessary files * Modify to stop ExecutorService using shutdownNow * Modify to use ScheduledExecutor managed by FrameworkExecutorRepository * Synchronize reconnectDuration with HeaderExchangeClient's reconnectDuration * get framework model directly use awaitility |
||
|---|---|---|
| .. | ||
| dubbo-remoting-api | ||
| dubbo-remoting-http | ||
| dubbo-remoting-netty | ||
| dubbo-remoting-netty4 | ||
| dubbo-remoting-zookeeper | ||
| dubbo-remoting-zookeeper-curator5 | ||
| pom.xml | ||