I agree with your're assessment. While i wasn't able to fix the specific issue, I was able to remove some functionality that was not actually needed (updating rows in the DB), as well as move to Read Committed for the Isloation level. Now I'm running with 10 threads with no problem.
On Feb 1, 3:57 pm, Corey Kaylor <[email protected]> wrote: > I do remember under certain circumstances though that when the DTC callback > occurs it can crash the application. In other words, I don't believe it's > something we can catch. This same thing can happen with Linq to SQL or > Entity Framework also. > > The lines that are suspect... > > System.Transactions.Oletx.OutcomeEnlistment.InvokeOutcomeFunction(System.Transactions.TransactionStatus) > at > System.Transactions.Oletx.OletxTransactionManager.ShimNotificationCallback(System.Object, > Boolean) > at > System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(System.Object, > Boolean) -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
