BUG: DependentTransaction, incorrect thread synchronization results in db serialization exception

[bpipe]

Code: Select all

        [TestMethod]
        public void TestUpdate()
        {
            for (int i = 0; i < 1000; i++)
            {
                using (TransactionScope tx = new TransactionScope())
                {
                    DependentTransaction depTx = Transaction.Current.DependentClone(DependentCloneOption.BlockCommitUntilComplete);
                    System.Threading.Tasks.Task.Factory.StartNew(() =>
                                                                     {
                                                                         Thread.Sleep(100);
                                                                         depTx.Complete();
                                                                     });
//var connection = CreateConnection(); //pseudo code
// connection.Update("UPDATE test SET value='bar' WHERE key='foo'"); //pseudo code
                    tx.Complete();
                }
            }
        }

[bpipe]

As a workaround you can use your own thread sync methods, like:

Code: Select all

        [TestMethod]
        public void TestUpdate()
        {
            for (int i = 0; i < 1000; i++)
            {
                using (TransactionScope tx = new TransactionScope())
                {
                    DependentTransaction depTx = Transaction.Current.DependentClone(DependentCloneOption.RollbackIfNotComplete);
                    var t = System.Threading.Tasks.Task.Factory.StartNew(() =>
                                                                     {
                                                                         Thread.Sleep(100);
                                                                         depTx.Complete();
                                                                     });
// Do SQL Update here
                    t.Wait();
                    tx.Complete();
                }
            }
        }

[Pinturiccio]

We have reproduced the issue. We will investigate it and post here about the results as soon as possible.