Is there any way to change Transaction's MaxTimeout or any plan to make possible it?

[JP3BGY]

https://github.com/dotnet/corefx/blob/a4f5f13ec1fa0d51ce0964c126e35ef0046ea7be/src/System.Transactions.Local/src/System/Transactions/Configuration/MachineSettingsSection.cs#L7-L26

It seems there is no way to change Transaction's MaxTimeout in .NET Core.
Is there any way to change it or any plan to make it possible?

[dasetser]

@JP3BGY You're correct that there is no way to change the Transaction's MaxTimeout in .NET Core. In .NET Framework the only way was through machine config, which does not exist on .NET Core, so this is always the default value of 10 minutes.

We don't have any plans to add a new way to configure this. You generally want to design your transactions so they are short-lived to avoid locking resources for extended periods of time.

[GSPP]

@dasetser I work on two major applications that require long-running transactions. These are transactions for background jobs. The blocking that this causes has no end user impact. We need the atomicity so that failed jobs are rolled back. The transaction duration for such jobs ranges from milliseconds to a few hours.

There is nothing inherently bad about long-running transactions. They do require more careful design but it's a useful feature to have.

We could manually manage the transactions but we currently (and for good reasons) depend on System.Transactions for our transaction management.

This would be a migration issue for us. Any chance you can add a setting for this?

I'd prefer setting the timeout in code to the machine.config anyway.

[dasetser]

That scenario sounds reasonable. I'll reopen this issue. Unfortunately I don't think we'll have time to get to this in the next release, so I'll leave this in future for now.

If this is something you need sooner I would suggest looking into the code linked in the initial issue report and making a PR for us to review. It looks like it would just be getting rid of this MachineSettingsSection that doesn't currently do anything and adding an API you can use to set it instead.