re: After the timeout

Adam Machanic — Wed, 09 Jan 2013 20:47:24 GMT

Hi Alex,

I don't think that your conclusion logically follows... here's a slightly reformatted version:

"If we return the connection to the pool and if it is reused, the transaction will be rolled back."

Rephrase the second "if" as a "when" and now you have a problem -- because you can't tell me, with any certainty, when that connection will be reused and the transaction rolled back. Which means that you can have a transaction sitting there holding some resource locks for a long time. Maybe even blocking someone else, whose command didn't time out (yet).

So my conclusion would be different than yours. It would be: "You should always roll back any active transaction after a timeout."

--Adam

re: After the timeout

Alexander Kuznetsov — Wed, 09 Jan 2013 21:04:55 GMT

Hi Adam,

I agree, and I have already implemented two extension methods that roll back active transactions, as well as edited my post.

Thanks!