Anon2Tokyo commented on issue #13853: URL: https://github.com/apache/dubbo/issues/13853#issuecomment-5207189190
@AlbumenJ This appears to have been fixed by #13904 (`f03823eec`, "Use ExecutorService instead of event loop for Netty connection"). The reconnect scheduling path no longer uses `future.channel().eventLoop().schedule(...)`; it now schedules reconnects through `connectivityExecutor.schedule(...)` in `AbstractNettyConnectionClient`. I think this issue can be closed as fixed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
