[Mono-bugs] [Bug 80343][Wis] New - Threads are using TransactionScope of each other

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Dec 22 11:01:18 EST 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by adriaanvk at gmail.com.


--- shadow/80343	2006-12-22 11:01:18.000000000 -0500
+++ shadow/80343.tmp.1154	2006-12-22 11:01:18.000000000 -0500
@@ -0,0 +1,51 @@
+Bug#: 80343
+Product: Mono: Class Libraries
+Version: 1.2
+OS Details: 
+Status: NEW   
+Priority: Wishlist
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: adriaanvk at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Threads are using TransactionScope of each other
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+in an application using System.Transactions in multithreaded system,
+threads are using the same ambient transaction instead of separate per
+thread / context.
+Steps to reproduce the problem:
+1. Create an application with System.Transactions support (lets say, a save
+2. Create a test which calls the save method via a new threads. Start 20
+simulatius threads
+3. You see that the threads sometimes used the same transactionscope, which
+is wrong, because the scope is defined in the save method itself, not over
+all called save methods.
+Actual Results:
+Exceptions that the Current Transactionscope has been changed, or
+Transaction has been aborted, because other threads has already committed
+your transaction
+Expected Results:
+Threads used all separate ambient transaction
+How often does this happen? always in multithreaded system when two threads
+uses both a transactionscope at the same time.
+Additional Information:
+Have a patch for it

More information about the mono-bugs mailing list