RapperCL opened a new issue, #7267:
URL: https://github.com/apache/rocketmq/issues/7267

   ### Before Creating the Bug Report
   
   - [X] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq/discussions).
   
   - [X] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [X] I have confirmed that this bug belongs to the current repository, not 
other repositories of RocketMQ.
   
   
   ### Runtime platform environment
   
   window 10
   
   ### RocketMQ version
   
   develop(5.1.3)
   
   ### JDK Version
   
   JDK 1.8.0_372
   
   ### Describe the Bug
   
   Condition judgment error
   code path: 
org.apache.rocketmq.remoting.netty.NettyRemotingAbstract#invokeAsyncImpl
   When obtaining semaphore resource timeout, if the timeout <= 0, then a 
timeout exception should be thrown , otherwise a invoke that is too fast 
exception will be thrown.
   
![image](https://github.com/apache/rocketmq/assets/44110731/64853ac8-9541-4ffc-a0b9-af8e396d20b6)
   
   
   ### Steps to Reproduce
   
   Code level defects
   
   ### What Did You Expect to See?
   
   When obtaining semaphore resource timeout, if the timeout <= 0, then a 
timeout exception should be thrown , otherwise a invoke that is too fast 
exception will be thrown.
   
   ### What Did You See Instead?
   
   When obtaining semaphore resource timeout, if the timeout <= 0, then a a 
invoke that is too fast exception  be thrown , otherwise a timeout exception be 
thrown.
   
   ### 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

Reply via email to