Re: [WebDNA] online.db deadlock: your current options ...
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106926
interpreted = N
texte = I just had a though ..... it could be virus checking software that is =causing the problem !If you disallow the SW from accessing .db files that may solve the =problem. I must check my own configuration !!RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 11/07/2011, at 10:39 PM, Kenneth Grome wrote:>> 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.=20>=20> This probably just confirms that the problem is in a recent=20> Windows update, especially if the old server has NOT been=20> updated.>=20>=20>> 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>=20> There is no WebDNA access to a SQL db in the code you=20> posted, so unless WebDNA is accessing SQL somewhere=20> elsewhere (and creating this problem there) you're wasting=20> yout time looking at SQL issues.>=20>=20>> I am considering moving this functionality into>> MSSQL, as that would at least resolve the deadlock>> problem, or so I hope.>=20> It would, assuming the deadlock issue occurs only when=20> WebDNA cannot access its online.db file. =20>=20> But WebDNA is faster than SQL so you may end up with SQL=20> "not keeping up" with your web traffic if you make this=20> change, so it probably wouldn't hurt to look at other=20> options first ...>=20>=20>> I am not sure how to have anyone look at it, when I am=20>> not able to determine where the problem(s) originate ...>=20> We (I) think it's a Windows config issue, or some other=20> software on the server that is improperly blocking WebDNA's=20> access to the "online.db" file. =20>=20> If this is true you could do more online research to=20> possibly learn which software is "doing the wrong thing"=20> then reconfigure or get rid of that software. And if this=20> still doesn't help I suppose you could hire a Windows expert=20> to figure out what's going on and then fix it for you.=20>=20> ------------------->=20> Or just skip all this diagnostic stuff and convert the=20> online.db functions to SQL as you suggested above. =20>=20> It is entirely possible that SQL will not be overloaded by=20> your heavy web traffic, and if this is the case your deadlock=20> problem will be eliminated once and for all -- at least on=20> the online.db.=20>=20> Sincerely,> Kenneth Grome> ---------------------------------------------------------> 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:
I just had a though ..... it could be virus checking software that is =causing the problem !If you disallow the SW from accessing .db files that may solve the =problem. I must check my own configuration !!RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 11/07/2011, at 10:39 PM, Kenneth Grome wrote:>> 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.=20>=20> This probably just confirms that the problem is in a recent=20> Windows update, especially if the old server has NOT been=20> updated.>=20>=20>> 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>=20> There is no WebDNA access to a SQL db in the code you=20> posted, so unless WebDNA is accessing SQL somewhere=20> elsewhere (and creating this problem there) you're wasting=20> yout time looking at SQL issues.>=20>=20>> I am considering moving this functionality into>> MSSQL, as that would at least resolve the deadlock>> problem, or so I hope.>=20> It would, assuming the deadlock issue occurs only when=20> WebDNA cannot access its online.db file. =20>=20> But WebDNA is faster than SQL so you may end up with SQL=20> "not keeping up" with your web traffic if you make this=20> change, so it probably wouldn't hurt to look at other=20> options first ...>=20>=20>> I am not sure how to have anyone look at it, when I am=20>> not able to determine where the problem(s) originate ...>=20> We (I) think it's a Windows config issue, or some other=20> software on the server that is improperly blocking WebDNA's=20> access to the "online.db" file. =20>=20> If this is true you could do more online research to=20> possibly learn which software is "doing the wrong thing"=20> then reconfigure or get rid of that software. And if this=20> still doesn't help I suppose you could hire a Windows expert=20> to figure out what's going on and then fix it for you.=20>=20> ------------------->=20> Or just skip all this diagnostic stuff and convert the=20> online.db functions to SQL as you suggested above. =20>=20> It is entirely possible that SQL will not be overloaded by=20> your heavy web traffic, and if this is the case your deadlock=20> problem will be eliminated once and for all -- at least on=20> the online.db.=20>=20> Sincerely,> Kenneth Grome> ---------------------------------------------------------> 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
Stuart Tremain
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:
AOL and webcat (1998)
WebDNA deletes major DB data big time (2004)
Shopping carts and reloading pages (1997)
Bug alert! (1997)
WebCat b13 CGI -shownext- (1997)
Me know logical no need Now totally OT (2002)
Nesting format tags (1997)
Encyption mail was Suggestions for Topics ... (1998)
Wanted: More Math Functions (or, Can You Solve This?) (1997)
Url encoded fun (1998)
Nested search (1997)
Range of Reports- go relational or include file? (2000)
bug in [SendMail] (1997)
Download (1999)
Showing unopened cart (1997)
embedding [showcart] ??? (1998)
ReturnRaw Returns (2000)
WC2.0 Memory Requirements (1997)
listfiles, moving files (1998)
inconsistent webcat calculation? (1997)