I think I am having the same issue. I have noticed that I sometimes get an exception on another thread. The other thread seems to be setup by the distributed transaction.
Perhaps try the code I pasted into my issue and see what happens ... http://groups.google.com/group/nhusers/browse_thread/thread/de1e4fc825b41a03 Option 2, do you mean create a new session for each transaction? That is a good idea to me. I have been unable to use the same session, as randomly the session decides it cannot disconnect as the transaction has not been commited. On Apr 15, 7:21 pm, Norman <[email protected]> wrote: > This seems to be an NHibernate bug that is specific to Oracle. > > I've raised a Jira (NH-2176) for this and provided a failing unit > test: > > http://216.121.112.228/browse/NH-2176 -- 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.
