[WebDNA] online.db deadlock: your current options ...
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106902
interpreted = N
texte = > With regards to duplicating the error, I tried forcing > the issue on our previous webserver, we still have this > computer - it is just tucked away ready to be gutted and > recycled - and I could not replicate the error. This probably just confirms that the problem is in a recent Windows update, especially if the old server has NOT been updated. > With regarding to the MSSQL and the online.db lock, I > don't think they related the online.db has no relation > to the MSSQL server, the MSSQL handles a lot of other > things There is no WebDNA access to a SQL db in the code you posted, so unless WebDNA is accessing SQL somewhere elsewhere (and creating this problem there) you're wasting yout time looking at SQL issues. > I am considering moving this functionality into > MSSQL, as that would at least resolve the deadlock > problem, or so I hope. It would, assuming the deadlock issue occurs only when WebDNA cannot access its online.db file. But WebDNA is faster than SQL so you may end up with SQL "not keeping up" with your web traffic if you make this change, so it probably wouldn't hurt to look at other options first ... > I am not sure how to have anyone look at it, when I am > not able to determine where the problem(s) originate ... We (I) think it's a Windows config issue, or some other software on the server that is improperly blocking WebDNA's access to the "online.db" file. If this is true you could do more online research to possibly learn which software is "doing the wrong thing" then reconfigure or get rid of that software. And if this still doesn't help I suppose you could hire a Windows expert to figure out what's going on and then fix it for you. ------------------- Or just skip all this diagnostic stuff and convert the online.db functions to SQL as you suggested above. It is entirely possible that SQL will not be overloaded by your heavy web traffic, and if this is the case your deadlock problem will be eliminated once and for all -- at least on the online.db. Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
> With regards to duplicating the error, I tried forcing > the issue on our previous webserver, we still have this > computer - it is just tucked away ready to be gutted and > recycled - and I could not replicate the error. This probably just confirms that the problem is in a recent Windows update, especially if the old server has NOT been updated. > With regarding to the MSSQL and the online.db lock, I > don't think they related the online.db has no relation > to the MSSQL server, the MSSQL handles a lot of other > things There is no WebDNA access to a SQL db in the code you posted, so unless WebDNA is accessing SQL somewhere elsewhere (and creating this problem there) you're wasting yout time looking at SQL issues. > I am considering moving this functionality into > MSSQL, as that would at least resolve the deadlock > problem, or so I hope. It would, assuming the deadlock issue occurs only when WebDNA cannot access its online.db file. But WebDNA is faster than SQL so you may end up with SQL "not keeping up" with your web traffic if you make this change, so it probably wouldn't hurt to look at other options first ... > I am not sure how to have anyone look at it, when I am > not able to determine where the problem(s) originate ... We (I) think it's a Windows config issue, or some other software on the server that is improperly blocking WebDNA's access to the "online.db" file. If this is true you could do more online research to possibly learn which software is "doing the wrong thing" then reconfigure or get rid of that software. And if this still doesn't help I suppose you could hire a Windows expert to figure out what's going on and then fix it for you. ------------------- Or just skip all this diagnostic stuff and convert the online.db functions to SQL as you suggested above. It is entirely possible that SQL will not be overloaded by your heavy web traffic, and if this is the case your deadlock problem will be eliminated once and for all -- at least on the online.db. Sincerely, Kenneth Grome
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:
Listserver problem (1997)
Size limit for tmpl editor ? (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
WebCat2b15MacPlugin - showing [math] (1997)
PCS Frames (1997)
[HIDEIF] inside [FOUNDITEM] (1997)
What is the maximum record length? (1998)
Vanity counter side note (1998)
Public beta 5 of WebCatalog 4.0 is now available (2000)
Can't Search field (1998)
Printing a final order (1997)
[Announce]: Web server security and password protection (1997)
Thanks ! (1997)
Revisit: speed test (2002)
Robust WebDNA Job Manager / Accountant (2006)
OFF-TOPIC: No messages since Saturday (1998)
Shipping Based on Number of Items (1998)
webdelivery.tmpl???? (1997)
RePost: NAT and the CART (1999)
Error (1997)