3424672656 opened a new issue, #8261: URL: https://github.com/apache/rocketmq/issues/8261
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary ![image](https://github.com/apache/rocketmq/assets/125714719/8fcc8bf5-9af3-484b-a79c-daba9c2d5f11) public Message request(final Message msg, long timeout) Internal logic ![image](https://github.com/apache/rocketmq/assets/125714719/d6734ef1-b0bc-47cc-9fbf-9c50e01533dc) ![image](https://github.com/apache/rocketmq/assets/125714719/582ec4ee-b1a7-4103-933e-83f7c0f95ed2) ![image](https://github.com/apache/rocketmq/assets/125714719/d2bfd2bd-f14f-45f0-8ee8-c482ac937e58) Use countDownLatch to implement synchronization logic, but the thread is forced to wake up only after a timeout, and to wait until the timeout returns after a successful responseļ¼Therefore, after a successful response, the countDown() function should be called to wake up the thread to return, and do not do ineffective sleep ### Motivation Avoid unnecessary waiting when a response is successfully returned ### Describe the Solution You'd Like after a successful response, the countDown() function should be called to wake up the thread to return, and do not do ineffective sleep ### Describe Alternatives You've Considered null ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org