Hi All,
I tested the WITH LOCK feature in July of 2014 with 3.0 and a simple 
application and works like a charm. Now I want to use it in production 
but the same test app give deadlocks. The database contains one table 
with one row and a BIGINT field increased by 1 500 times by the test 
app. In 2014 started the test app in 10 instances when all finished the 
BIGINT field value is 5000. Now 3 instances enough to got deadlock after 
some time. Is this a bug? If I know correctly a wait transaction wait 
forever and not give any error on lock conflict. The used transaction is 
read committed no record version (MON$ISOLATION_MODE is 3, 
MON$LOCK_TIMEOUT is -1). Tried with SuperServer (Linux 64bit and Windows 
32bit).
Gabor
------------------------------------
------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------------
Yahoo Groups Links
<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/firebird-support/
<*> Your email settings:
    Individual Email | Traditional
<*> To change settings online go to:
    http://groups.yahoo.com/group/firebird-support/join
    (Yahoo! ID required)
<*> To change settings via email:
    firebird-support-digest@yahoogroups.com 
    firebird-support-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
    firebird-support-unsubscribe@yahoogroups.com
<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/
No comments:
Post a Comment