IMHO this is one of the weakest points of NHibernate: not supporting TransactionScope. This is THE transaction API of .NET...
RP On Monday, August 12, 2013 5:04:41 PM UTC+1, [email protected] wrote: > > > > On Sunday, August 4, 2013 7:34:20 PM UTC+1, Oskar Berggren wrote: >> >> >> >> So far, the best advice is to ensure that you always use NHibernate's own >> transaction object in addition to TransactionScope, and to always >> commit/rollback the nhibernate transaction before disposing the >> TransactionScope. Does the problem occur even in this scenario? >> >> > Unfortunately, attempting to combine NHibernate transactions with > TransactionScope fairly reliably crashes the application, no matter which > way round they're nested. Threading-related state corruption seems to occur > much more readily in this situation. We're using SysCache2 as well, which > might be a contributing factor. > > Removing the NHibernate transaction was actually our 'fix' for the > problem, although running the code often enough can still cause a crash > occasionally. > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
