| Subject | Re: [firebird-support] Lost transactions that causes deadlocks |
|---|---|
| Author | Ann W. Harrison |
| Post date | 2005-06-21T18:24:18Z |
Peter Ypenburg wrote:
be causing deadlocks. In theory, when one transaction finds itself
blocks by another, the first thing it tries to do is determine if the
blocking transaction is alive or dead. The involves signaling it and
is, I think, implemented in SuperServer with a check that the connection
is currently active and working at both ends. If not, the blocking
transaction is declared dead and rolled back, undoing the block.
Are you seeing some other behavior?
Ann
>Err... Interesting question. If the transaction is lost, it shouldn't
> I need to understand how to handle lost transactions that causes deadlocks.
be causing deadlocks. In theory, when one transaction finds itself
blocks by another, the first thing it tries to do is determine if the
blocking transaction is alive or dead. The involves signaling it and
is, I think, implemented in SuperServer with a check that the connection
is currently active and working at both ends. If not, the blocking
transaction is declared dead and rolled back, undoing the block.
Are you seeing some other behavior?
>Regards,
Ann