mz0113 opened a new issue, #15839: URL: https://github.com/apache/dubbo/issues/15839
### 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 3.2.18 openjdk21 ### Steps to reproduce this issue Issue Description: When building a consumer-provider application using JDK 21 deployed on an intranet server: 1. The consumer-side runs on an 8-core CPU and 8GB RAM machine with JVM -Xmx parameter set to 4GB. 2. RPC communication uses the Triple protocol with a message size of ~900KB (approximately 1MB). 3. Under 100 concurrent RPC calls (issue reproduces at just 15 concurrency), all RPC requests fail immediately with the error: T**otalPendingBytes size overflow for stream** After testing, in JDK 21, whether business threads use virtual threads or platform threads to initiate Dubbo RPC requests, the error conclusion remains unchanged – both cases result in the same error. ### What you expected to happen "I want to resolve this error because under the exact same configuration (**JDK 8 + Dubbo 3.0.12 + Triple protocol**), my tests run without errors. However, the error occurs with Dubbo 3.2.18 and JDK 21." **what i want to know is why it happend in jdk21 + dubbo 3.2.18 , but not happend in JDK 8 + Dubbo 3.0.12 ;** i have read some issue ralated this , but i **didn`t find a offical method** to resolve it and **didn`t find a really reason** for it ... ### Anything else _No response_ ### 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]
