RE: [WebDNA] Connection Timeout
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112269
interpreted = N
texte = Ha imagine finding you here!! You could have just called me :)=20 # # KeepAliveTimeout: Number of seconds to wait for the next request from = the # same client on the same connection. # KeepAliveTimeout 15 There is also the "timeout" setting which defaults to 120 however, I = think the one above should do the trick. Keith ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DISCLAIMER:=A0 Any views expressed in this message are those of the = individual sender. This email and any attachments to it may contain confidential information and may be legally privileged.=A0 If you are not the = intended recipient, you must not review, transmit, convert to hard copy, copy, = use or disseminate this email or any attachment to it. If you have received = this email in error, please immediately notify the originator by return email = and delete this message. Please note that if this email contains a forwarded message or is a reply to a prior message, some or all of the contents of this message or any attachments may not have been produced by this = office. -----Original Message----- From: Michael Davis [mailto:admin@network13.net]=20 Sent: Wednesday, April 08, 2015 5:59 PM To:
Subject: [WebDNA] Connection Timeout I have a process that connects to a remote server via TCPConnect within = a founditems loop, which can end up taking a long time to complete. = Within the loop, I write out to a log file. The web page will eventually throw = an internal server error when Apache times out. But I can tail the log = file and see that the WebDNA process runs to completion. Is there a way to = tune Apache to a longer timeout value or otherwise keep the connection to the FCGI alive while it's still actively processing the request? And thanks, too, for helping out my good friend, and new square bracket head, Keith Scarzafava. Thanks, Mike
Associated Messages, from the most recent to the oldest:
Ha imagine finding you here!! You could have just called me :)=20 # # KeepAliveTimeout: Number of seconds to wait for the next request from = the # same client on the same connection. # KeepAliveTimeout 15 There is also the "timeout" setting which defaults to 120 however, I = think the one above should do the trick. Keith ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DISCLAIMER:=A0 Any views expressed in this message are those of the = individual sender. This email and any attachments to it may contain confidential information and may be legally privileged.=A0 If you are not the = intended recipient, you must not review, transmit, convert to hard copy, copy, = use or disseminate this email or any attachment to it. If you have received = this email in error, please immediately notify the originator by return email = and delete this message. Please note that if this email contains a forwarded message or is a reply to a prior message, some or all of the contents of this message or any attachments may not have been produced by this = office. -----Original Message----- From: Michael Davis [mailto:admin@network13.net]=20 Sent: Wednesday, April 08, 2015 5:59 PM To: Subject: [WebDNA] Connection Timeout I have a process that connects to a remote server via TCPConnect within = a founditems loop, which can end up taking a long time to complete. = Within the loop, I write out to a log file. The web page will eventually throw = an internal server error when Apache times out. But I can tail the log = file and see that the WebDNA process runs to completion. Is there a way to = tune Apache to a longer timeout value or otherwise keep the connection to the FCGI alive while it's still actively processing the request? And thanks, too, for helping out my good friend, and new square bracket head, Keith Scarzafava. Thanks, Mike
"Keith Scarzafava"
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:
sendmail (2000)
ConvertChars? (1998)
OT - how many HTML forms is too many? (2000)
The beginning (1997)
[shownext] and descending order (1997)
Listserver problem (1997)
problems with 2 tags (1997)
Multiple database stuff... (1999)
Date problems (1997)
Re:Item options w/ price adjustment (1997)
Problems with shopping cart (1997)
Stopping bad HTML propagation ? (1997)
New public beta available (1997)
[WebDNA] Pages dying (2008)
[WebDNA] Using Grep to pull links from a variable (2014)
Cookies (1998)
all records returned. (1997)
CMS - Formatting Content (2004)
won't serve .tpl (2000)
Frames and WebCat (1997)