I have forked the Rhino Service Bus repository to: https://github.com/hjalet/rhino-esb
and added a unit test that reproduces our scenario: https://github.com/hjalet/rhino-esb/blob/master/Rhino.ServiceBus.Tests/Bugs/When_transaction_disposed_nested_transactions_fail.cs A few things to note about the test: 1. I attempt to dispose the nested transaction in several event handlers in my test message module simply to illustrate that none of them are called before the outer transaction is disposed and thus causing the exception. 2. I verify the error by looking in the log4net output simply because the transaction exception is caught by the Rhino Service Bus code and simply logged (in the MessageHandlingCompletion class). So this is the only way I could think of to verify if the exception occured. The exception itself can also be seen in the console output of the test (since I configure log4net). Let me know if you can see a way around this. If not I can implement a fix and send you guys a pull request. Regards René -- 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/-/jA1VZXWlxSYJ. 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.
