-
-
Notifications
You must be signed in to change notification settings - Fork 279
Implement Redis transport scheduling for messages #2003
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
Implement Redis transport scheduling for messages #2003
Conversation
…mediate and scheduled sends, and integrate tests for scheduled message flow
…nce RedisTransport and RedisStreamListener for configurable behavior
|
@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; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you need to change that one back. That is for enrollment in the transactional inbox/outbox
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I was trying few things and forgot to take this out. I fixed it now.
|
@sdesaiLULA Hey, just one small issue that won't impact any of your tests I'd think |
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]