Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SagaException silently ignored by NHibernateSagaRepository

See original GitHub issue

I have following problem: when my saga throws NotAcceptedStateMachineException then problematic event is not moved to error queue.

Exception is throwed here.

Then it is consumed by DefaultUnhandledEventCallback, which converts it to UnhandledEventException.

Then it is catched in SendToInstance method, which converts it to SagaException, which exception is silently ignored here.

Here’s whole stack trace:

at Automatonymous.AutomatonymousStateMachine1.DefaultUnhandledEventCallback(UnhandledEventContext1 context) at Automatonymous.AutomatonymousStateMachine1.UnhandledEvent(EventContext1 context, State state) at Automatonymous.States.StateMachineState1.<Automatonymous-State<TInstance>-Raise>d__271.MoveNext() — End of stack trace from previous location where exception was thrown — at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Automatonymous.AutomatonymousStateMachine1.<Automatonymous-StateMachine<TInstance>-RaiseEvent>d__211.MoveNext() — End of stack trace from previous location where exception was thrown — at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Automatonymous.Pipeline.StateMachineSagaMessageFilter2.<Send>d__5.MoveNext() --- End of inner exception stack trace --- at Automatonymous.Pipeline.StateMachineSagaMessageFilter2.<Send>d__5.MoveNext() — End of stack trace from previous location where exception was thrown — at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MassTransit.NHibernateIntegration.Saga.NHibernateSagaRepository1.<SendToInstance>d__101.MoveNext() — End of stack trace from previous location where exception was thrown — at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MassTransit.NHibernateIntegration.Saga.NHibernateSagaRepository1.<SendQuery>d__81.MoveNext()

Is it intended behavior or rethrow is missing here?

Issue Analytics

State:
Created 7 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

czesiucommented, Feb 23, 2017

Hi. Same problem occurs here. Exception is silently ignored.

@phatboyg: Should I create new issue or you can reopen this?

0reactions

alexeyzimarevcommented, Feb 26, 2017

No I meant you changed both in that commit

Top Results From Across the Web

Saga Data Tables Not Created When using NHibernate ...

When I got to the database, I notice that there is no table called OrderPolicyData. My assumption is that the saga tables are...

NServiceBus Sagas using NHibernate - Unable to connect ...

I have found a workaround to my problem. It seems to be an issue with using the built-in NServiceBus profiles.

NHibernate Persistence Saga Concurrency

Updating or deleting saga data No exceptions will be thrown. Conflicts cannot occur because the persistence uses pessimistic locking.

NServiceBus on .NET Core - It's time - Particular Software

In SQL Persistence, each saga will get its own table, but it will store saga data as a ... an exception raised within...

EDA – Udi Dahan – The Software Simplist

NServiceBus comes with an NHibernate-based saga persister for exactly this reason, though any persistence mechanism which allows you to query on something other ......