Re: gateway application timeouts
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18548
interpreted = N
texte = We used to have WebCat and WebStar freezes. Most of the time, the computer froze hard and not even the mouse or clock moved. These happened more frequently under heavy loads. We figured that OT was overloaded with incoming requests while WebCat was hogging the processor and everything locked up. Occasionally we saw what you describe, which is just WebCat freezing up but restartable.Our path to stability included getting rid of possibility of large search results (who needs to surf through thousands of results). The server didn't become rock solid until we off-loaded the graphics onto another server. Now there's no conflict between WebCat hogging the processor and Webstar serving the graphics. I'd follow Ken's suggestions of minimizing work done by WebCat - ie don't run pages through WebCat unnecessarily. I'd also run some RAM checker programs to make sure all the chips are good. You'd be suprised at how poor the quality control is for RAM these days. Since WebCat is RAM based, that could really upset the server. Perhaps just increasing RAM allocation would help too.We've been very stable for months now since offloading the graphics.Good luck!Sandy >Thanks, Ken. > >Powerkey waits 6 minutes before forcing a restart. Nothing we do could >take that long. Webcat just freezes and never comes back to life. 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). We have max >connections set to 30 on this server so it's not exactly busy. And it is >very random. > >>But if you cannot use the plugin you could try increasing the connection >>time allowed in your web server software to see if that helps. If that >>doesn't work, then you need to look at your WebCat code and figure out >>what task it is performing that's taking it so long to process ... >> >>Sincerely, >>Ken Grome >>808-737-6499 >>WebDNA Solutions >>mailto:ken@webdna.net >>http://www.webdna.net > > > >Regards, >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:
We used to have WebCat and WebStar freezes. Most of the time, the computer froze hard and not even the mouse or clock moved. These happened more frequently under heavy loads. We figured that OT was overloaded with incoming requests while WebCat was hogging the processor and everything locked up. Occasionally we saw what you describe, which is just WebCat freezing up but restartable.Our path to stability included getting rid of possibility of large search results (who needs to surf through thousands of results). The server didn't become rock solid until we off-loaded the graphics onto another server. Now there's no conflict between WebCat hogging the processor and Webstar serving the graphics. I'd follow Ken's suggestions of minimizing work done by WebCat - ie don't run pages through WebCat unnecessarily. I'd also run some RAM checker programs to make sure all the chips are good. You'd be suprised at how poor the quality control is for RAM these days. Since WebCat is RAM based, that could really upset the server. Perhaps just increasing RAM allocation would help too.We've been very stable for months now since offloading the graphics.Good luck!Sandy >Thanks, Ken. > >Powerkey waits 6 minutes before forcing a restart. Nothing we do could >take that long. Webcat just freezes and never comes back to life. 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). We have max >connections set to 30 on this server so it's not exactly busy. And it is >very random. > >>But if you cannot use the plugin you could try increasing the connection >>time allowed in your web server software to see if that helps. If that >>doesn't work, then you need to look at your WebCat code and figure out >>what task it is performing that's taking it so long to process ... >> >>Sincerely, >>Ken Grome >>808-737-6499 >>WebDNA Solutions >>mailto:ken@webdna.net >>http://www.webdna.net > > > >Regards, >Karl Schroll >Digital Frontier, http://www.digitalfrontier.com >1813 Mountain Road, PO Box 1171 >Stowe, VT 05672 USA >802-253-8612 > > >
Sandra L. Pitner
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:
Database Repopulation (2004)
Error Log.db --however (1997)
'does not contain' operator needed ... (1997)
Tuition - UK (2000)
Quitting WebMerchant ? (1997)
WebCatalog can't find database (1997)
Field validation problem (1999)
CMS - Formatting Content (2004)
anyone have an automated template encrypter? (2000)
WC 2.0 frames feature (1997)
Kaaaaahhhhhhhnnnnnnn! (1997)
Multiple Merchant Accounts? (1997)
WebCatalog can't find database (1997)
Flag checking (2000)
Express Lane (2000)
webcat (2000)
Separate SSL Server (1997)
4.01 broken pages using ShowNext (2000)
Clean Code: Rules for inserting keyboard returns? (1997)
dos performance (1998)