c# - TransactionScope timeout weirdness with TransactionScopeOption.RequiresNew -


Something strange is going on here.

I have just added a transaction radius around some legacy code.

  "Transaction Manager Remote / Remote Support is disabled. Network transaction. " 

Work / non-removal (without a code change or reconstruction) between a line [literally 3F 5S [web app]) . This was the local code connecting to a remote DB server.

For this reason, completely different code times in a different project are ending. If I remove the transaction then this code runs properly, but with this time it comes out.

What's going on?

Edit: I have found that by changing my Transaction Skaps:

 using  (var scope = new Transaction Scope (TransactionScopeOption.RequiresNew)).  

P>

"post-text" itemprop = "text">

between intervals:

  (var scope = new transaction scope (TransactionScopeOption.RequiresNew) )  

and

  (var scope = new TransactionScope ())  

The second is that the current ( Environment) transactions can be reused, whereas the first one creates a new transaction within an old transaction.

Transactions within a transaction require a distributed transaction coordinator.

Then there are three possible reasons for your error:

  • MSDTC is not running
  • Your database is on a separate machine and the window is configured from the network's transaction To not allow.
  • Your database is on a different machine and UL server is configured not to allow the transaction to the network

Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -