Re: What is this error message?

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66521
interpreted = N
texte = Perhaps exclusivelock either works successfully or fails after the preset timeout period without reporting any error? I don't remember details like this any more, but it might not hurt to check the docs for exclusivelock and see how it actually behaves ... And I'm sure you have already done this, but just as a reminder to others, don't forget to confirm that the db changes you're doing inside the exclusivelock context are actually being saved. Sincerely, Kenneth Grome owner@kengrome.com kengrome@gmail.com www.kengrome.com On Mon, 27 Mar 2006 23:38:31 -0600, Gary Krockover wrote: > Hi Sal, > > Well, Googling for the exact phrase "failed to acquire lock on > database" only brings up 2 hits, and those are to the change history > log for WebDNA. Interestingly, this error message is listed: > > 1/13/2003 4.5.1 > General release of WebDNA 4.5.1 for all supported platforms > Changes / Additions > All Platforms > Database error messages have been improved to report more detail on > why a database failed to load (or be accessed). These include: > > Not Enough memory to load database. > Failed to acquire lock on database <-- > Database file not found or opened > Bad database format (with 'Merge' style databases) > > So I'm guessing that it means that it couldn't get read access to the > database, though we don't know why. At any rate, an ExclusiveLock > cleared up that error message from appearing and removing an old > search and then replace within a founditems for the newer > replacefounditems fixed the problem of the page loading slowly. How > or why this suddenly broke is beyond me, but $hit happens. :) > > Thanks, > Gary > > At 10:53 PM 3/27/2006, you wrote: >> The error seems to show up on numerous sites. The common thread seems >> to have something to do with website stats. >> >> Copy this into Google and take a look. >> Failed to aquire lock on database - Possible deadlock averted >> >> Sal D'Anna > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: What is this error message? ( "Palle B. Nielsen (PowerPalle)" 2006)
  2. Re: What is this error message? ( Gary Krockover 2006)
  3. Re: What is this error message? ( "Palle B. Nielsen (PowerPalle)" 2006)
  4. Re: What is this error message? ( Donovan Brooke 2006)
  5. Re: What is this error message? ( Kenneth Grome 2006)
  6. Re: What is this error message? ( Gary Krockover 2006)
  7. Re: What is this error message? ( "sal danna" 2006)
  8. Re: What is this error message? ( Gary Krockover 2006)
  9. Re: What is this error message? ( Donovan Brooke 2006)
  10. Re: What is this error message? ( Gary Krockover 2006)
  11. What is this error message? ( Gary Krockover 2006)
Perhaps exclusivelock either works successfully or fails after the preset timeout period without reporting any error? I don't remember details like this any more, but it might not hurt to check the docs for exclusivelock and see how it actually behaves ... And I'm sure you have already done this, but just as a reminder to others, don't forget to confirm that the db changes you're doing inside the exclusivelock context are actually being saved. Sincerely, Kenneth Grome owner@kengrome.com kengrome@gmail.com www.kengrome.com On Mon, 27 Mar 2006 23:38:31 -0600, Gary Krockover wrote: > Hi Sal, > > Well, Googling for the exact phrase "failed to acquire lock on > database" only brings up 2 hits, and those are to the change history > log for WebDNA. Interestingly, this error message is listed: > > 1/13/2003 4.5.1 > General release of WebDNA 4.5.1 for all supported platforms > Changes / Additions > All Platforms > Database error messages have been improved to report more detail on > why a database failed to load (or be accessed). These include: > > Not Enough memory to load database. > Failed to acquire lock on database <-- > Database file not found or opened > Bad Database format (with 'Merge' style databases) > > So I'm guessing that it means that it couldn't get read access to the > database, though we don't know why. At any rate, an ExclusiveLock > cleared up that error message from appearing and removing an old > search and then replace within a founditems for the newer > replacefounditems fixed the problem of the page loading slowly. How > or why this suddenly broke is beyond me, but $hit happens. :) > > Thanks, > Gary > > At 10:53 PM 3/27/2006, you wrote: >> The error seems to show up on numerous sites. The common thread seems >> to have something to do with website stats. >> >> Copy this into Google and take a look. >> Failed to aquire lock on database - Possible deadlock averted >> >> Sal D'Anna > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Kenneth Grome

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:

transferring values (1998) WebCatalog [FoundItems] Problem - AGAIN - (1997) Re:no [search] with NT (1997) Expiration of Carts (1997) For Sale: WebTen 2.x and WebCat 2.x (2000) Shownext never shows next...still (1997) Date fun with MySQL (2004) Missing from Docs [folderName] (1997) ThreadMem ignored? (1998) OT: Poll Please (2002) Can't find templaes (1997) Shownext and Jumping between pages (2000) text size limitation (1997) Wanted: Broader string manipulation functions (1997) Re:no [search] with NT (1997) Emailer help....! (1997) Running 2 two WebCatalog.acgi's (1996) Help with Shipping Costs (1997) RE: Languages (1997) Text limits in NT version? (1997)