The follow code illustrate the problem:


It seems that in SessionImpl.AfterTransactionCompletion() didn't set transaction to null, so that my query will reuse a disposed transaction. I added transaction = null; and it works fine.

My I correct?

I got the same problem (I think), after transaction commit, any other query fails.
If I set transaction = null I get
"Cannot access a disposed object named 'AdoTransaction'"

Yes, a bug slipped in and was already reported in JIRA, I'll fix it.

Is this fixed in the cvs version?

Hi,

As far as I can see, this renders the CurrentSession.Transaction.WasCommitted and CurrentSession.Transaction.WasRolledBack properties unusable after a committed or rolled back transaction has occurred.

"Object Reference not set to an instance of an object" because the transaction is disposed.

Not really sure whether these properties are useful anyway... Opinion?

Cheers,

Mike

Ok I changed the fix so that those properties work again.

WasCommitted and WasRolledback seem to be of no value.

I have a transaction that failed and I want to rollback the transaction so I have this code



but if I try to do the rollback I get this error:

This SqlTransaction has completed; it is no longer usable.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable.

So what is the proper way to determine if I should do the rollback or if it has been done for me and the transaction is closed?

Sergey, Is this the expected behavior?