Implement Redis transport scheduling for messages#2003
Merged
jeremydmiller merged 5 commits intoJasperFx:mainfrom Jan 12, 2026
Merged
Implement Redis transport scheduling for messages#2003jeremydmiller merged 5 commits intoJasperFx:mainfrom
jeremydmiller merged 5 commits intoJasperFx:mainfrom
Conversation
…mediate and scheduled sends, and integrate tests for scheduled message flow
…nce RedisTransport and RedisStreamListener for configurable behavior
Member
|
@sdesaiLULA Dude, you've been on fire lately! |
…ty; verify scheduling and retry behavior
|
|
||
| // Redis Streams work well in buffered mode by default | ||
| Mode = EndpointMode.BufferedInMemory; | ||
| Mode = EndpointMode.Durable; |
Member
There was a problem hiding this comment.
I think you need to change that one back. That is for enrollment in the transactional inbox/outbox
Contributor
Author
There was a problem hiding this comment.
Thanks, I was trying few things and forgot to take this out. I fixed it now.
Member
|
@sdesaiLULA Hey, just one small issue that won't impact any of your tests I'd think |
This was referenced Jan 14, 2026
This was referenced Mar 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds comprehensive integration tests for Redis-backed endpoints in Wolverine, focusing on database-backed endpoint scheduling/retries and native dead letter queue (DLQ) support. The new tests ensure that scheduled retries, dead letter queue operations, and related behaviors work correctly with Redis as a transport.
Key additions and improvements:
Database-backed endpoint scheduling and retries:
DatabaseBackedEndpointTeststo verify that Redis stream endpoints implementIDatabaseBackedEndpoint, correctly schedule retries (with and without explicit scheduled times), and that scheduled messages are picked up by polling and moved to the stream as expected.Dead letter queue (DLQ) functionality:
DeadLetterQueueTeststo test that failed messages are moved to the Redis dead letter queue, DLQ entries contain detailed exception information, and the DLQ key format is correct. Also verifies that disabling DLQ prevents the creation of the dead letter stream.DeadLetterQueueTrackerandFailingCommandHandlerto simulate and track message failures for DLQ testing.Test infrastructure and coverage:
TestMessage,TestMessageHandler,FailingCommand,FailingCommandHandler) to facilitate message publishing and failure simulation in tests. [1] [2]