views:

547

answers:

1

Any one ever seen this? It comes from a .net remoting endpoint hosted in IIS with a 16 process web garden. So there are many concurrent transactions in each thread pool per process. We are using linq to sql and the Transaction object that is from the DataContext, NOT the transactionScope object. It seems to happen either around the dispose for the connection or the dispose for the transaction after the commit.

+1  A: 

I found the problem. This exception is throw after a Change Conflict has occurred with a linq object in the domain. Once the change conflict has been throw from datacontext.submitchanges, if you then attempt to rollback the transaction, the transaction.Rollback with throw the exception described above.

kazakdogofspace