I've recently upgraded to Nhibernate 3.3 (from 2.1) and now I have a problem with objects not being released from memory. It seems that it is waiting for a transaction to be committed however I am not using explicit transactions and in monitoring the database I can see that the changes have already been saved. It appears that if I add explicit transactions it resolves the memory problem but then creates other deadlock issues at the database level. Has there been some change in 3 which requires some different patterns to clear the implicit transactions? If I look at the object retention graph I see some classes named NHibernate.Action.BeforeTransactionComplete... which are holding onto the objects. Are implicit transaction not supported any longer? (spare me the advice on the danger of implicit transactions)
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/6kl624p6UnkJ. 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.
