You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Clone Wolverine repos
Launch Samples/EfCoreSample/ItemService project in debug mode
Put a breakpoint on Handle method of ItemCreatedHandler class
Make an http request to /items/create4 endpoint
Breakpoint is never reached
Expected behavior
Code execution shoud stop on breakpoint, the handler shoud have been called.
Additional context
Wolverine 3.5.1
The text was updated successfully, but these errors were encountered:
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:
Expected behavior
Code execution shoud stop on breakpoint, the handler shoud have been called.
Additional context
Wolverine 3.5.1
The text was updated successfully, but these errors were encountered: