wx-wsq opened a new issue, #16294: URL: https://github.com/apache/dubbo/issues/16294
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo Java 2.7.0 OpenJDK 1.8 -Xms512M -Xmx1024M CentOS Linux 7 ### Steps to reproduce this issue Set the dubbo.consumer.timeout property on the consumer to 300000 (300s) and then loop call provider with data volumes exceeding 10000. It will trigger OOM in two minutes. The reason is that even if the request has ended, consumers cannot immediately release the data and need to wait for the data to timeout on its own. <img width="1144" height="1541" alt="Image" src="https://github.com/user-attachments/assets/13a839ff-8410-4638-a526-5c68171a5e8a"; /> ### What you expected to happen not trigger OOM ### Anything else This issue is 100% reproducible. I noticed that fixes have been added to version 2.7.23, but my project is not easy to upgrade. Is there a solution that can be solved in version 2.7.0？ ### Do you have a (mini) reproduction demo? - [ ] Yes, I have a minimal reproduction demo to help resolve this issue more effectively! ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
