HI Jason, thanks for the reply. An upgrade to NH3 isn't really possible yet. We use quite a bit of NH- Linq and I've read the new provider fails where the last one succeeds, which would be a bit of a regression test problem. I'm waiting for NH 3.1 before I consider upgrading.
I'm a little confused though as Davy's post definitely describes a Timeout failure with the above test (it's taken from his blog at http://davybrion.com/blog/2010/05/avoiding-leaking-connections-with-nhibernate-and-transactionscope), but if you say it's memory leak, then fair enough. I've noticed in another recent post that Fabio mentions NH 3.0 fixes the issue because: >NH has 2 transaction factories: >AdoNetWithDistributedTransactionFactory (default) >AdoNetTransactionFactory (was default in previous versions) I'm wondering if I can just configure NH 2.1.2GA to use AdoNetWithDistributedTransactionFactory instead and the potential problem will resolve itself? -- You received this message because you are subscribed to the Google Groups "nhusers" group. 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/nhusers?hl=en.
