[Bug] dubbo.consumer.timeout setting too long leads to OOM

[wx-wsq]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues 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.

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

• I agree to follow this project's Code of Conduct

[zrlw]

Dubbo 2.7 hasn't been maintained for a while, you might bump version to solve it.

[wx-wsq]

Dubbo 2.7 hasn't been maintained for a while, you might bump version to solve it.

This project is already very old, and I want to avoid upgrading as much as possible. Is there any solution in 2.7.0.