Skip to content

[Host.RabbitMq] Handle RabbitMQ RPC deserialization failures - #481

Open
zarusz wants to merge 1 commit into
masterfrom
feature/480
Open

[Host.RabbitMq] Handle RabbitMQ RPC deserialization failures#481
zarusz wants to merge 1 commit into
masterfrom
feature/480

Conversation

@zarusz

@zarusz zarusz commented Jul 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • send request/response error replies when request deserialization fails before handler invocation
  • keep RabbitMQ from replaying background processing failures onto the next delivery, avoiding stuck unacked malformed messages
  • add focused processor and concurrent decorator coverage

Fixes #480

Tests

  • dotnet test src\Tests\SlimMessageBus.Host.Test\SlimMessageBus.Host.Test.csproj --no-restore -v minimal -p:UseSharedCompilation=false -m:1 -nodeReuse:false
  • dotnet test src\Tests\SlimMessageBus.Host.RabbitMQ.Test\SlimMessageBus.Host.RabbitMQ.Test.csproj --no-restore -v minimal --filter "FullyQualifiedName!~IntegrationTests" -p:UseSharedCompilation=false -m:1 -nodeReuse:false

Note: full RabbitMQ integration tests require a local broker on 127.0.0.1:5672; without it they fail with BrokerUnreachableException.

@zarusz zarusz changed the title Handle RabbitMQ RPC deserialization failures [Host.RabbitMq] Handle RabbitMQ RPC deserialization failures Jul 27, 2026
Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
@zarusz zarusz self-assigned this Jul 31, 2026
@zarusz zarusz added this to the 3.6.0 milestone Jul 31, 2026
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[RabbitMQ] Deserialization failure in request/response consumer silently discards message without sending error response to requester

1 participant