Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106889
interpreted = N
texte = We did. This might happens if Windows locks a file that WebDNA is trying = to write to, or if there are multiple instances of WebDNA running and = trying to write to a single database. I do not think the multiple = instance case is the problem here. WebDNA spits out an error first = before deadlocking. This is why i think we need to know why Windows = would lock a WebDNA database, and why this happens suddenly (and = regularely) after years of error-free service. If this comes from = WebDNA, a reinstall would solve the problem. In this case, i believe = Windows (an update, a specific module or extension) is to blame. - chris On Jul 10, 2011, at 19:52, Stuart Tremain wrote: > Very strange that this problem is happening to another Windows Server = user. I reported the same problem last week on a system that has been = running for 5+ years and have NEVER seen the problem in 12+ years of = WebDNA experience. >=20 > The problem tends to create a loop and brings the server to a grinding = halt by constantly using 100% of CPU. >=20 > After reading the many rants in this thread I do suspect that it MAY = be a Windows problem brought about from a Windows update. >=20 > "Failed to aquire lock on database - Possible deadlock averted" >=20 > The error that is being published in the errorlog.txt does not come = from the errormessages.db so must be coming from the WebDNA engine = itself. >=20 > Chris, maybe you could look into this please. >=20 >=20 > Regards >=20 > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 > On 07/07/2011, at 5:10 AM, Tommy Bell wrote: >=20 >> Hello everyone, a few days ago a post was made about=20 >> "Failed to aquire lock on database" >>=20 >> I have been experiencing this for quite some time, and recently it = has gotten much worse, I was hoping someone could enlighten me to where = to go bug hunting, or just offer some tips with regards to what I could = be doing wrong. >>=20 >> This is the error i get (One amongst many db's, not just online.db) >> An unknown error occurred: >> DBError >> ../../database/online.db >> Failed to aquire lock on database - Possible deadlock averted >>=20 >> /Tommy >>=20 >>=20 >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us
Associated Messages, from the most recent to the oldest:
We did. This might happens if Windows locks a file that WebDNA is trying = to write to, or if there are multiple instances of WebDNA running and = trying to write to a single database. I do not think the multiple = instance case is the problem here. WebDNA spits out an error first = before deadlocking. This is why i think we need to know why Windows = would lock a WebDNA database, and why this happens suddenly (and = regularely) after years of error-free service. If this comes from = WebDNA, a reinstall would solve the problem. In this case, i believe = Windows (an update, a specific module or extension) is to blame. - chris On Jul 10, 2011, at 19:52, Stuart Tremain wrote: > Very strange that this problem is happening to another Windows Server = user. I reported the same problem last week on a system that has been = running for 5+ years and have NEVER seen the problem in 12+ years of = WebDNA experience. >=20 > The problem tends to create a loop and brings the server to a grinding = halt by constantly using 100% of CPU. >=20 > After reading the many rants in this thread I do suspect that it MAY = be a Windows problem brought about from a Windows update. >=20 > "Failed to aquire lock on database - Possible deadlock averted" >=20 > The error that is being published in the errorlog.txt does not come = from the errormessages.db so must be coming from the WebDNA engine = itself. >=20 > Chris, maybe you could look into this please. >=20 >=20 > Regards >=20 > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 > On 07/07/2011, at 5:10 AM, Tommy Bell wrote: >=20 >> Hello everyone, a few days ago a post was made about=20 >> "Failed to aquire lock on database" >>=20 >> I have been experiencing this for quite some time, and recently it = has gotten much worse, I was hoping someone could enlighten me to where = to go bug hunting, or just offer some tips with regards to what I could = be doing wrong. >>=20 >> This is the error i get (One amongst many db's, not just online.db) >> An unknown error occurred: >> DBError >> ../../database/online.db >> Failed to aquire lock on database - Possible deadlock averted >>=20 >> /Tommy >>=20 >>=20 >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebDNA server not running (2003)
[foundItems] context problem (2000)
[isfile] ? (1997)
Date search - yes or no (1997)
Sense/Disallow HTML tags during $Append (1997)
Max Record length (1997)
IIS4b2 and WebCatalog b19 (1997)
Error:Too many nested [xxx] contexts (1997)
Using the sendmail command on CGate Pro (Unix) (2000)
customer.db and forms (1999)
Interfacing WebMerchant to www.fedex.com (1997)
FTP Settings (1999)
Help! WebCat2 bug (1997)
Custom Error Pages in Apache (2006)
Using Plug-In while running 1.6.1 (1997)
[OT] html background att (2003)
View order not right (1997)
OT: RAID Options (2004)
Strange intermittent WebDNA problems (2008)
What am I missing (1997)