Skip to content

Fix outbox failed batch retry loop#474

Closed
zarusz wants to merge 1 commit into
masterfrom
fix/outbox-failed-batch-retry-loop
Closed

Fix outbox failed batch retry loop#474
zarusz wants to merge 1 commit into
masterfrom
fix/outbox-failed-batch-retry-loop

Conversation

@zarusz

@zarusz zarusz commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Summary

  • Fixes [Host.RabbitMq] Outbox retries exhaust quickly when broker is down #459 by stopping failed outbox batches from immediately re-entering the same sending pass.
  • Failed messages still have delivery attempts recorded, but the next retry is governed by the outbox polling/lock timing instead of a tight same-instance loop.
  • Adds core outbox unit coverage and PostgreSQL/Testcontainers integration coverage for the retry behavior.

Tests

  • dotnet test src\Tests\SlimMessageBus.Host.Outbox.Test\SlimMessageBus.Host.Outbox.Test.csproj --no-build -v minimal -m:1
  • dotnet test src\Tests\SlimMessageBus.Host.Outbox.PostgreSql.Test\SlimMessageBus.Host.Outbox.PostgreSql.Test.csproj --no-build -v minimal -m:1

Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
@zarusz zarusz force-pushed the fix/outbox-failed-batch-retry-loop branch from e7fe14c to 7c78365 Compare June 17, 2026 17:40
@zarusz zarusz closed this Jun 17, 2026
@zarusz zarusz deleted the fix/outbox-failed-batch-retry-loop branch June 17, 2026 17:41
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.

[Host.RabbitMq] Outbox retries exhaust quickly when broker is down

1 participant