Transaction Scope some times partially commit Problem ? Why?

Question

0.00/5 (No votes)

See more:

Hi Friends,

I have used TransactionScope class for transaction handling in ASP.NET
but some times it works as partially commit.

Can any one tell me why and how to resolve this issue ?

I was googling, but got no satisfying solution.

Please help me
Shreeniwas

Posted 27-May-13 18:16pm

shreeniwas kushwah

Updated 27-May-13 18:33pm

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ)

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) · Answer 1 · 2013-05-27T18:54:00

Refer - [MSDN] Transaction Scope[^].

Quote:
Limitations of System.Transactions

The System.Transactions namespace is not supported by .NET Compact Framework 2.0. Therefore, implementation will be for the Windows desktop operating system only and will correspond with the .NET Framework 2.0, .NET Framework 3.0, .NET Framework 3.5 or .NET Framework 4.

Note that if there is a timeout, the System.Transactions infrastructure will call Rollback from a separate thread. The main thread will not know about a rollback occurring in the separate thread. The long transactions might see a non-deterministic behavior and partial commit scenarios. To resolve this, increase the timespan of the transaction scope object when you create the object.

You can use any constructor listed here - [MSDN] TransactionScope Constructor[^] for the same.