Skip to content
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

WolverineHttp Endpoints with Transactional behavior & Durable queues don't trigger handlers #1184

Closed
blashbul opened this issue Dec 24, 2024 · 1 comment · Fixed by #1189
Closed
Labels
bug Something isn't working

Comments

@blashbul
Copy link

Describe the bug
When using Wolverine Http endpoint, that return an event message, havingTransactional Attribute set ( Using AutoApplyTransactions give same results), using durable local queues, the message is written to database in the wolverine_incoming_envelopes table, but is never procedded and thus never triggers the handlers bound to the event.

To Reproduce
Steps to reproduce the behavior:

  1. Clone Wolverine repos
  2. Launch Samples/EfCoreSample/ItemService project in debug mode
  3. Put a breakpoint on Handle method of ItemCreatedHandler class
  4. Make an http request to /items/create4 endpoint
  5. Breakpoint is never reached

Expected behavior
Code execution shoud stop on breakpoint, the handler shoud have been called.

Additional context
Wolverine 3.5.1

@jeremydmiller
Copy link
Member

@blashbul Thanks for the report. Nuget dependency problems, but then, this was a real Wolverine.HTTP + EF Core permutation problem. Fix in 3.6 soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants