Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Produce async no need retry when the request is already timeout. #8168

Closed
3 tasks done
humkum opened this issue May 20, 2024 · 0 comments · Fixed by #8169
Closed
3 tasks done

[Bug] Produce async no need retry when the request is already timeout. #8168

humkum opened this issue May 20, 2024 · 0 comments · Fixed by #8169

Comments

@humkum
Copy link
Contributor

humkum commented May 20, 2024

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.
image
image

Steps to Reproduce

Producer add a RPCHook
image
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant