Subject | deadlock - update conflicts with concurrent update |
---|---|
Author | Sean |
Post date | 2007-06-06T14:34:31Z |
In my heavy loaded server application I sometimes see exceptions of
---------
FirebirdSql.Data.FirebirdClient.FbException: deadlock
update conflicts with concurrent update
---------
When using a blank database it doesn't have the problem. But after
running for a couple of days when the database size becomes bigger
(around 1GB), the exception happens more and more...
I am using firebird 1.5.4, .net provider 2.0.1. The connection pool
size is 1000, basically caches all db connections. Sometimes there may
be 100 threads spawned trying to insert/update records.
What can I do to avoid update conflicts as much as possible? shall I
limit the thread number or connection pool size?
Thanks a lot!
Sean
---------
FirebirdSql.Data.FirebirdClient.FbException: deadlock
update conflicts with concurrent update
---------
When using a blank database it doesn't have the problem. But after
running for a couple of days when the database size becomes bigger
(around 1GB), the exception happens more and more...
I am using firebird 1.5.4, .net provider 2.0.1. The connection pool
size is 1000, basically caches all db connections. Sometimes there may
be 100 threads spawned trying to insert/update records.
What can I do to avoid update conflicts as much as possible? shall I
limit the thread number or connection pool size?
Thanks a lot!
Sean