Skip to content

Last offset fix #407

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

Merged
merged 3 commits into from
Mar 26, 2025
Merged

Last offset fix #407

merged 3 commits into from
Mar 26, 2025

Conversation

jonnepmyra
Copy link
Contributor

This change ensures that the reliable consumer tracks the lastOffsetConsumed correctly, allowing it to reconnect to the correct offset in the event of a reconnection.

Before this PR:
The lastOffsetConsumed was recorded before the message handler was executed, which could result in potential message loss during connection issues or consumer reconnections.

After this PR:
The lastOffsetConsumed will be stored after the message handler is executed, preventing message loss in the event of connection issues or reconnections.

Falk Jonas - HK added 3 commits March 26, 2025 07:33
…ler is called. This change does it after the messagehandler is called in order to avoid potential messageloss on the event of connection-issues/reconnecting-consumer
@Gsantomaggio Gsantomaggio merged commit 7ea9728 into rabbitmq:main Mar 26, 2025
2 checks passed
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 this pull request may close these issues.

2 participants