We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
CentOS
develop
JDK 11
The PopCk is incorrect when consuming messages from one broker, forwarding them to another broker as is, and then consuming them from the new broker.
The correct PopCk should be used.
PopCk is incorrect.
No response
The text was updated successfully, but these errors were encountered:
[ISSUE apache#7531] Clear POP_CK when sending messages
9adcd46
e970dcb
cca3ac0
[ISSUE #7531] Clear POP_CK when sending messages (#7532)
00965d8
Successfully merging a pull request may close this issue.
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
CentOS
RocketMQ version
develop
JDK Version
JDK 11
Describe the Bug
The PopCk is incorrect when consuming messages from one broker, forwarding them to another broker as is, and then consuming them from the new broker.
Steps to Reproduce
What Did You Expect to See?
The correct PopCk should be used.
What Did You See Instead?
PopCk is incorrect.
Additional Context
No response
The text was updated successfully, but these errors were encountered: