No-SilverBullet opened a new issue, #116: URL: https://github.com/apache/dubbo-getty/issues/116
**What happened**: When the dubbo provider reports a connection error, such as exceeding the upper limit of provider accepts, reConnect() will cause the client to continuously reconnect, causing the client's CPU and memory to continue to increase. Here is the call chain : <img width="1116" alt="image" src="https://github.com/apache/dubbo-getty/assets/112961281/b80bd923-659f-4cf1-8d0c-58cc531dfada";> <img width="756" alt="image" src="https://github.com/apache/dubbo-getty/assets/112961281/4360e92a-63c7-4b41-afe7-e3df136e1152";> <img width="869" alt="image" src="https://github.com/apache/dubbo-getty/assets/112961281/63945990-943c-4aad-8dbe-0dad1fdfac9f";> **What you expected to happen**: I think that when there is a problem with the TCP connection, the practice of maintaining the connection pool should be temporarily stopped **How to reproduce it (as minimally and precisely as possible)**: In dubbo settings, set the getty-session-param's connection-number less than the provider's accepts will cause this problem. **Anything else we need to know?**: -- 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: notifications-unsubscr...@dubbo.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For additional commands, e-mail: notifications-h...@dubbo.apache.org
