Re: [WebDNA] [tcpconnect] timeout
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112311
interpreted = N
texte = I have noticed that the default timeout on the FastCGI servers I have = worked on are shorter.=20 There is a directive to edit that, depending on which FastCGI you are = using. Sincerely, Donovan On May 19, 2015, at 4:22 PM, Stuart Tremain
wrote: > Thanks for the info Chris >=20 > Shame about the SSL as that is where I am needing it. Is this = something that can/will be addressed ? >=20 > You mention FastCGI, but does this work with the server edition. >=20 >=20 > Kind regards >=20 > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 >=20 >> On 19 May 2015, at 21:49, christophe.billiottet@webdna.us wrote: >>=20 >> [tcpconnect] tiemout has not been documented voluntarily; However, I = will provide some technical information here: >>=20 >> example: >>=20 >> [tcpconnect host=3Dinternic.net&port=3D43&timeout=3D60] >> [tcpsend]XXXXXX[/tcpsend] >> [/tcpconnect] >>=20 >> This will only work on Linux for the initial connect(), OSX will keep = the default timeout length when connect()ing. But after the connection = is open all operating systems will use that timeout for read() and = write() to the tcp connection. >>=20 >> It does *not* work for SSL connections. >>=20 >>=20 >> If you want timeout longer than 30s, you will have to adjust some = FastCGI parameters too. For example, a Linux server running mod_fcgid = will need you to lengthen IOTimeout: >>=20 >> FcgidCmdOptions /var/www/WebDNA/WebDNA.fcgi MaxProcesses 1 = IdleTimeout 120 IOTimeout 120 >>=20 >> test: >>=20 >> After I do this it does in fact let me wait 60 seconds: >> 18:02:24 >> Error: couldn=92t connect to host [XX.XX.XX.XX] >> 18:03:24 >>=20 >> If you don=92t do this then a 60 second connect timeout will cause = WebDNA.fcgi to be killed by mod_fcgi and you will get a 500 internal = server error. >>=20 >> - chris >>=20 >>=20 >>=20 >>> On May 19, 2015, at 14:25, Stuart Tremain = wrote: >>>=20 >>> Could this please be documented ? >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>> --------------------------------------------------------- >>> 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 >> --------------------------------------------------------- >> 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 > --------------------------------------------------------- > 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
Associated Messages, from the most recent to the oldest:
I have noticed that the default timeout on the FastCGI servers I have = worked on are shorter.=20 There is a directive to edit that, depending on which FastCGI you are = using. Sincerely, Donovan On May 19, 2015, at 4:22 PM, Stuart Tremain wrote: > Thanks for the info Chris >=20 > Shame about the SSL as that is where I am needing it. Is this = something that can/will be addressed ? >=20 > You mention FastCGI, but does this work with the server edition. >=20 >=20 > Kind regards >=20 > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 >=20 >> On 19 May 2015, at 21:49, christophe.billiottet@webdna.us wrote: >>=20 >> [tcpconnect] tiemout has not been documented voluntarily; However, I = will provide some technical information here: >>=20 >> example: >>=20 >> [tcpconnect host=3Dinternic.net&port=3D43&timeout=3D60] >> [tcpsend]XXXXXX[/tcpsend] >> [/tcpconnect] >>=20 >> This will only work on Linux for the initial connect(), OSX will keep = the default timeout length when connect()ing. But after the connection = is open all operating systems will use that timeout for read() and = write() to the tcp connection. >>=20 >> It does *not* work for SSL connections. >>=20 >>=20 >> If you want timeout longer than 30s, you will have to adjust some = FastCGI parameters too. For example, a Linux server running mod_fcgid = will need you to lengthen IOTimeout: >>=20 >> FcgidCmdOptions /var/www/WebDNA/WebDNA.fcgi MaxProcesses 1 = IdleTimeout 120 IOTimeout 120 >>=20 >> test: >>=20 >> After I do this it does in fact let me wait 60 seconds: >> 18:02:24 >> Error: couldn=92t connect to host [XX.XX.XX.XX] >> 18:03:24 >>=20 >> If you don=92t do this then a 60 second connect timeout will cause = WebDNA.fcgi to be killed by mod_fcgi and you will get a 500 internal = server error. >>=20 >> - chris >>=20 >>=20 >>=20 >>> On May 19, 2015, at 14:25, Stuart Tremain = wrote: >>>=20 >>> Could this please be documented ? >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>> --------------------------------------------------------- >>> 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 >> --------------------------------------------------------- >> 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 > --------------------------------------------------------- > 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
Donovan Brooke
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:
[Price] (1997)
Requiring that certain fields be completed (1997)
Simple question (1998)
Getting Emailer to send mail (1997)
California Tax Rates (1998)
Free pack for the New UPS ratings and services tool (2000)
%@#*& back button!!! (1999)
Problems with [Applescript] (1997)
Credit Card Checksum (1997)
Locking up with WebCatalog... (1997)
SMSI: WebDNA Versions? (2002)
Archives... (1997)
WebCat hosting providers? (1997)
Date comparison using showif (2003)
[Semi-OT] Eaaaaaasy OSX FTP (2003)
validatin (1998)
TeaRoom (2000)
[WebDNA] OSX users (2009)
WebCatalog dying in NT (1998)
Webcat no longer supported? (2006)