Bug 31197 - TransactionScope ignores timeout
Summary: TransactionScope ignores timeout
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Data ()
Version: 4.0.0
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-06-17 12:08 UTC by Shay Rojansky
Modified: 2018-02-22 22:36 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Shay Rojansky 2015-06-17 12:08:29 UTC
mono's implementation of TransactionScope does not enforce the timeout, looking at the sources nothing is done with it whatsoever.

To reproduce:

using (var scope = new TransactionScope(TransactionScopeOption.Required, new TimeSpan(0, 0, 1)))
   using (var conn = new NpgsqlConnection(....))  // or some other database
       var cmd = new NpgsqlCommand(@"INSERT INTO data (name) VALUES ('HELLO')", conn);
       cmd.ExecuteNonQuery(); // just some update

This code should fail with a timeout exception, but it does not.
Comment 1 Marek Safar 2018-02-22 22:36:07 UTC
Mono 5.10 has significantly improved System.Data implementation which should resolve this issue. If you can still reproduce it please reopen the issue.