This sqltransaction has completed; it is no longer usable. Connection still open

Question

1.00/5 (1 vote)

See more:

Hi everyone,

I'm having two sqlconnections that I'm trying to test. I purposely put some error on the second sql commandtext to force it to rollback everything, but I'm having an error when it hits the TransHQ.Rollback() in the second catch block. I knew about the "zombie transaction" thing, but all of my two connections are still open. Maybe I missed something.
This is my code:

VB

Try
    sqloCnHQ.Open()
    TransHQ = sqloCnHQ.BeginTransaction()
    cmdHQ.Transaction = TransHQ
    cmdHQ.Connection = sqloCnHQ
    cmdHQ.CommandText = SqlHQ.ToString()
    cmdHQ.CommandTimeout = 0
    cmdHQ.ExecuteNonQuery()
    TransHQ.Commit()
Catch ex As Exception
    Application.DoEvents()
    TransHQ.Rollback()
    ErrorHandling("Sync Transactions " & cmdHQ.ToString)
    SyncMessageOPT += "Sync Transactions " + cmdHQ.ToString + Environment.NewLine
    sqloCnHQ.Dispose()
    Err.Clear()
    Exit Sub
End Try


Try
    sqloCnLocal.Open()
    TransLocal = sqloCnLocal.BeginTransaction()
    cmdLocal.Transaction = TransLocal
    cmdLocal.Connection = sqloCnLocal
    cmdLocal.CommandText = SqlLocal.ToString() + "xxx"
    cmdLocal.CommandTimeout = 0
    cmdLocal.ExecuteNonQuery()
    TransLocal.Commit()
Catch ex As Exception
    Application.DoEvents()
    TransHQ.Rollback()
    TransLocal.Rollback()
    ErrorHandling("Sync Transactions " & cmdLocal.ToString)
    SyncMessageOPT += "Sync Transactions " + cmdLocal.ToString + Environment.NewLine
    sqloCnHQ.Dispose()
    sqloCnLocal.Dispose()
    Err.Clear()
    Exit Sub
End Try

sqloCnHQ.Dispose()
sqloCnLocal.Dispose()

Thanks in advance!

Posted 16-Sep-15 22:14pm

cedric003

Add a Solution

Comments

FrankNight 17-Sep-15 4:53am

Yes, you are missing something.
You need a "distributed transaction" that means a transaction across multiple database or connection.
You cannot manage it so simply.

Your code don't work because when you commit a transaction, it cannot be more rollbacked.

You can begin both transaction and commit (or rollback) in the same try/catch but is not a good practice.

Look for somthing like two-phase commit algorithm.
http://www.codeproject.com/Articles/143421/Two-Phase-Commit-Protocol

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)

cedric003 · Accepted Answer · 2015-09-17T15:59:00

Hi,

Thanks for the idea. I manage to get it right, but I'm not sure if what I did will have a drawback.I simply put the two commit statements after the second ExecuteNonQuery.

VB

sqloCnLocal.Open()
TransLocal = sqloCnLocal.BeginTransaction()
cmdLocal.Transaction = TransLocal
cmdLocal.Connection = sqloCnLocal
cmdLocal.CommandText = SqlLocal.ToString() + "xxx"
cmdLocal.CommandTimeout = 0
cmdLocal.ExecuteNonQuery()

TransHQ.Commit()
TransLocal.Commit()

So the idea is not to commit first until the whole execution finished.

Thanks for the great help!