Re: gateway application timeouts
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18541
interpreted = N
texte = Ken,>THis was happening to be when I was storing my dates in the default date >format, because interpreting dates in the dfault format is very >processor-intensive. That's why I changed all my stored dates to the >number of days since 00/00/0000. Now I never have a timeout problem >anymore, the date searching takes about 100 or 1000 times LESS TIME than >before. The difference is truly dramatic, especially in a large database.We switched to this date format several months ago and saw good results (not 1000x though, maybe 100x). That's not our problem.> >>And >>this can happen serving nothing more then a straight HTML page with NO >>webcat commands in it at all (at least that is the last page served before >>the crash, according to the WebCat debug file we keep). > >Do you use the tag in this last page even though >has no WebDNA tags in it? What's your InterpretAll preference set to? Is >WebCat actually serving this page or does it have a suffix that's not even >used by WebCatalog?We initially processed only .tmpl files (way way back) but now serve all .html and .tmpl through webcat. Both suffixes are served through webcat. Some pages have , some don't (our preferences don't require it).> >If WebCat is actually serving that last page, it may be doing it from a >different thread than the one that's causing the hang-ups, so the last >page in the logs is probably *not* always going to be the page that's >causing the problems -- but one of the last few pages in the logs *should* >include the problem page ... Can anyone from PCS confirm this? We were told months ago that the last page served in the debug file is the one that caused the problem...> >What's the server's timeout value set to? Have you tried doubling that >value to see if that change makes any difference?Offhand, I don't know what the timeout value is. I'll have a look at that tomorrow. I'm prety sure it's whatever the default value is. The server doesn't seem to be the problem. WebCat stops it dead in the water when WebCat hangs. A forced quit of WebCat and the server instantly starts serving again.> >Sincerely, >Ken Grome >808-737-6499 >WebDNA Solutions >mailto:ken@webdna.net >http://www.webdna.netRegards, Karl Schroll Digital Frontier, http://www.digitalfrontier.com 1813 Mountain Road, PO Box 1171 Stowe, VT 05672 USA 802-253-8612
Associated Messages, from the most recent to the oldest:
Ken,>THis was happening to be when I was storing my dates in the default date >format, because interpreting dates in the dfault format is very >processor-intensive. That's why I changed all my stored dates to the >number of days since 00/00/0000. Now I never have a timeout problem >anymore, the date searching takes about 100 or 1000 times LESS TIME than >before. The difference is truly dramatic, especially in a large database.We switched to this date format several months ago and saw good results (not 1000x though, maybe 100x). That's not our problem.> >>And >>this can happen serving nothing more then a straight HTML page with NO >>webcat commands in it at all (at least that is the last page served before >>the crash, according to the WebCat debug file we keep). > >Do you use the tag in this last page even though >has no WebDNA tags in it? What's your InterpretAll preference set to? Is >WebCat actually serving this page or does it have a suffix that's not even >used by WebCatalog?We initially processed only .tmpl files (way way back) but now serve all .html and .tmpl through webcat. Both suffixes are served through webcat. Some pages have , some don't (our preferences don't require it).> >If WebCat is actually serving that last page, it may be doing it from a >different thread than the one that's causing the hang-ups, so the last >page in the logs is probably *not* always going to be the page that's >causing the problems -- but one of the last few pages in the logs *should* >include the problem page ... Can anyone from PCS confirm this? We were told months ago that the last page served in the debug file is the one that caused the problem...> >What's the server's timeout value set to? Have you tried doubling that >value to see if that change makes any difference?Offhand, I don't know what the timeout value is. I'll have a look at that tomorrow. I'm prety sure it's whatever the default value is. The server doesn't seem to be the problem. WebCat stops it dead in the water when WebCat hangs. A forced quit of WebCat and the server instantly starts serving again.> >Sincerely, >Ken Grome >808-737-6499 >WebDNA Solutions >mailto:ken@webdna.net >http://www.webdna.netRegards, Karl Schroll Digital Frontier, http://www.digitalfrontier.com 1813 Mountain Road, PO Box 1171 Stowe, VT 05672 USA 802-253-8612
Karl Schroll
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:
taxTotal, grandTotal (1997)
typhoon... (1997)
RE: Credit card processing - UK (1997)
Browser Reloads and AddlineItem (1997)
Preventing Merchant Settling ? (1997)
Search Command, multiple dbs, etc. --further elucidation needed (2000)
[WebDNA] Instructions for install on CentOS 5.7? (2011)
One Hour Email (2002)
re: How can I record purchases to a database? (1998)
Generating Report Totals (1997)
Quitting WebMerchant ? (1997)
[WebDNA] [ipaddress] - [RealIP] - Not working properly (2016)
Database (2000)
db creator (2000)
Cookie Issue - No domain (2004)
WebCat2 several catalogs? (1997)
WCS Newbie question (1997)
To Use Cookies or Not To Use Cookies (2003)
RE: 2nd WebCatalog2 Feature Request (1996)
[WebDNA] [ipaddress] - [RealIP] - Not working properly (2016)