Re: gateway application timeouts
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18543
interpreted = N
texte = >>>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).If this is true, then you should set your prefs to NOT serve pages unless they have the tag in them. That way you can eliminate any possibility of WebCat trying to interpret something on those pages and getting jammed up for some unknown reason, because then you know for a fact that WebCat is ignoring those untagged pages.That's why I asked about your InterpretAll preference. If that pref is set to F, then you can easily eliminate the pages *without* that tag as potential problem pages ... which means it has to be one of the *other* pages (the ones with the tags) causing the problems ... >>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...Good idea to ask, because my understanding of multithreading is that with several threads running at the same time, one could be sitting there spinning its wheels while the others continue to send pages to the server where they would be logged and served as usual, thus making the problem page *NOT* the last page in the log ... >>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.You're probably right, but whenever you have a timeout error there's a possibility that you could fix it simply by increasing the timeout value so WebCat will have more time to return the page the server is waiting for. Try it and see what happens, maybe that's all you have to do! :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Associated Messages, from the most recent to the oldest:
>>>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).If this is true, then you should set your prefs to NOT serve pages unless they have the tag in them. That way you can eliminate any possibility of WebCat trying to interpret something on those pages and getting jammed up for some unknown reason, because then you know for a fact that WebCat is ignoring those untagged pages.That's why I asked about your InterpretAll preference. If that pref is set to F, then you can easily eliminate the pages *without* that tag as potential problem pages ... which means it has to be one of the *other* pages (the ones with the tags) causing the problems ... >>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...Good idea to ask, because my understanding of multithreading is that with several threads running at the same time, one could be sitting there spinning its wheels while the others continue to send pages to the server where they would be logged and served as usual, thus making the problem page *NOT* the last page in the log ... >>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.You're probably right, but whenever you have a timeout error there's a possibility that you could fix it simply by increasing the timeout value so WebCat will have more time to return the page the server is waiting for. Try it and see what happens, maybe that's all you have to do! :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
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:
Adding more than one item and QTY to cart (2000)
WebCat2b12 CGI Mac -- Problems propagating the cart through (1997)
Big Databases (1997)
hmmm (2006)
WCS Newbie question (1997)
Emailer setup (1997)
About [Loop] (2000)
Text data with spaces in them... (1997)
Exclamation point (1997)
WebCat2b15MacPlugin - [protect] (1997)
Email within tmpl ? (1997)
Cart Template (1997)
No comment (1997)
Using Plug-In while running 1.6.1 (1997)
Shipping.db (1998)
Price lookup problem - was Cart questions (1997)
WebCat2b12 - nesting [tags] (1997)
Two options to consider (2008)
WC 2.0 frames feature (1997)
AuthorizeNet Declines (2005)