Thanks for your input, but the exception remains. The problem lies in the fact that Rhino Service Bus disposes its outer transaction before any message module events are raised. It is the Dispose of the outer transaction that causes the exception because the inner exception has not been yet been disposed.
It all happens in the HandleMessageCompletion method of the MessageHandlingCompletion class in Rhino Service Bus. The first thing this method does, If an exception occur, is to dispose the outer transaction. Next it raises the appropriate events (message completed etc.). This led us to believe that some kind of BeforeDispose/BeforeRollback event is missing. We already have a BeforeMessageTransactionCommit event to handle our transaction in case of success. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/ERIZ_21HQrMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
