-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
PoolMessage and DLQ can not work together #13269
Comments
I'm working on this |
The issue had no activity for 30 days, mark with Stale label. |
The issue had no activity for 30 days, mark with Stale label. |
@hangc0276 @wangjialing218 I noticed that the solution proposed in the pull request for this bug has not been merged yet. Could you please provide an update on its status and let us know when we can expect this bug to be resolved? |
It looks like the PR has one commit/change request and some conflicts. Until those are resolved, we cannot merge the PR. |
Describe the bug
PoolMessage and DLQ can not work together
To Reproduce
Steps to reproduce the behavior:
consumer.negativeAcknowledge(message)
and then callmessage.release()
Expected behavior
The message should be sent to DLQ topic.
Additional context
The negative ack msgs will be sent to DLQ topic in a scheduler
triggerRedelivery
, when we enable poolMessages,message.release()
will clearMessageImpl
immediately, this will causeprocessPossibleToDLQ()
fail to get message id and resend to DLQ.The text was updated successfully, but these errors were encountered: