Hi all, I see quite a few bugs on JIRA relating to the same topic: https://nhibernate.jira.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+TransactionScope
They're all about the fact that SQL errors cause a session's SqlConnection to be closed from a different thread than the thread that opened it (through the AdoNetDistributedTransacionFactory). We've been running into this issue for quite some time now as well. We store NServiceBus saga's using NHibernate and occasionally we may get a deadlock. Normally this would not be a huge problem (just retry the message), but once this deadlock occurs, we get, for a minute or 2, a log full of errors like "New request is not allowed to start because it should come with valid transaction descriptor" and "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". Now, this is something we'd like to have fixed, or fix ourselves. Is anyone actively looking at this, right now? Or willing to share some suggestions/findings? Roy
