You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
CentOS7.3
RocketMQ version
5.2.0
JDK Version
Open_JDK 1.8.0_202
Describe the Bug
When producer send a message in async mode, if the request is timeout with throwing a RemotingTooMuchException, the producer would retry with �a negative value with timeoutMillis, which is not necessary.
Steps to Reproduce
Producer add a RPCHook
Try sleep 4s in in the doBeforeRequest function,to make the request cost time out.
What Did You Expect to See?
No retry when the request is already timeout.
What Did You See Instead?
The producer retry with a negative value of timeout, which will must failed, and it's unnecessary.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
CentOS7.3
RocketMQ version
5.2.0
JDK Version
Open_JDK 1.8.0_202
Describe the Bug
When producer send a message in async mode, if the request is timeout with throwing a RemotingTooMuchException, the producer would retry with �a negative value with timeoutMillis, which is not necessary.
Steps to Reproduce
Producer add a RPCHook
Try sleep 4s in in the doBeforeRequest function,to make the request cost time out.
What Did You Expect to See?
No retry when the request is already timeout.
What Did You See Instead?
The producer retry with a negative value of timeout, which will must failed, and it's unnecessary.
Additional Context
No response
The text was updated successfully, but these errors were encountered: