Subject | Deadlocks |
---|---|
Author | Milan Tomeš - Position |
Post date | 2011-06-03T06:25:31Z |
Hi all,
I'm having troubles with deadlocks in very strange behaviour.
Situation - one or more connections to a database, one running update
query per connection (long term query - more than hour) but every query
use some records which another query doesn't. Transactions are set to
wait, but I don't think this is a problem. There is a firebird.log entry
that says database name and "deadlock" message, but application freeze.
I have some lock print dumps (which Ann recommended me to make).
This problem happened in 2.1.4.18308 x64 and now is happening on
2.5.0.26074 x64 (both SuperServer). Server OS is W2008 R2 x64.
Any idea what to do to avoid this?
Thanks
Milan
I'm having troubles with deadlocks in very strange behaviour.
Situation - one or more connections to a database, one running update
query per connection (long term query - more than hour) but every query
use some records which another query doesn't. Transactions are set to
wait, but I don't think this is a problem. There is a firebird.log entry
that says database name and "deadlock" message, but application freeze.
I have some lock print dumps (which Ann recommended me to make).
This problem happened in 2.1.4.18308 x64 and now is happening on
2.5.0.26074 x64 (both SuperServer). Server OS is W2008 R2 x64.
Any idea what to do to avoid this?
Thanks
Milan