Re: [WebDNA] online.db deadlock: your current options ...
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106930
interpreted = N
texte = Thats quite a good idea, ill look into that when i get back from vacation /Tommy On 12-07-2011 01:01, Stuart Tremain wrote: > I just had a though ..... it could be virus checking software that is c= ausing the problem ! > > If you disallow the SW from accessing .db files that may solve the prob= lem. I must check my own configuration !! > > Regards > > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au > > > > > On 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. >> 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 >> --------------------------------------------------------- >> 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 > --------------------------------------------------------- > 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 Med Venlig Hilsen Tommy Dahlb=E6k Bell Tlf: +45 27 63 00 88 E-mail: tbell05@student.aau.dk E-mail: tommy@enkelthed.dk
Associated Messages, from the most recent to the oldest:
Thats quite a good idea, ill look into that when i get back from vacation /Tommy On 12-07-2011 01:01, Stuart Tremain wrote: > I just had a though ..... it could be virus checking software that is c= ausing the problem ! > > If you disallow the SW from accessing .db files that may solve the prob= lem. I must check my own configuration !! > > Regards > > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au > > > > > On 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. >> 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 >> --------------------------------------------------------- >> 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 > --------------------------------------------------------- > 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 Med Venlig Hilsen Tommy Dahlb=E6k Bell Tlf: +45 27 63 00 88 E-mail: tbell05@student.aau.dk E-mail: tommy@enkelthed.dk
Tommy Bell
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:
Error Lob.db records error message not name (1997)
quantity minimum problem (1997)
[OT]: BBEdit grep (2003)
Questions To Answer (1997)
writing cart to db (1998)
Setting up shop (1997)
Problems appending to database (1997)
WCS Newbie question (1997)
WebCatalog stalls (1998)
Banner DNA (1997)
credit card question (simple) (2001)
Formating found categories (1997)
Date search bug (1998)
WCS Newbie question (1997)
stumped on simple sort (1999)
Some Questions (1997)
Shopping Cart variation... (1997)
Resume Catalog ? (1997)
Pull Down Search (2000)
WebCatalog for guestbook ? (1997)