Jul 5, 2012 at 11:28 AM
Edited Jul 5, 2012 at 11:34 AM
I did some updates to our migration command line commands today, and I ran into a 'Session is closed!' exception where before I had no issues.
I have a loop that imports data 100 entries/time.
Before the loop I connect to the mysql backend (old data is on there) and demand a transaction.
First time in the loop @ start I create a 'RequiresNew' transaction scope, other times @ start I flush the content, clear it and complete+dispose the transaction scope, before creating a new one.
Sometimes I can 2, sometimes 4+ before I get said message.
Any ideas / hints where to start looking? :/
edit: Disabling Q42.DbTranslations resolved my problem - guess that is ok for now (since we'll only use these commands one time when migrating our data) but weird nonetheless :/