That sounds promising... But I don't see any CLIENTIOTIMEOUT entry. If none exists is it using the default? Do I add one in to change it.
Here is my clients.ini: [Witango Client Definitions] wapache.dll= wcgi.exe= wiis.dll= [wapache.dll] WITANGO_SERVER=127.0.0.1,18100 ERROR_HTML=C:\\Program Files\\Witango\\Server\\MiscFiles\\clienterror.html REPORTCLIENTERROR=TRUE [wiis.dll] WITANGO_SERVER=127.0.0.1,18100 ERROR_HTML=C:\\Program Files\\Witango\\Server\\MiscFiles\\clienterror.html REPORTCLIENTERROR=TRUE [wcgi.exe] WITANGO_SERVER=127.0.0.1,18100 ERROR_HTML=C:\\Program Files\\Witango\\Server\\MiscFiles\\clienterror.html REPORTCLIENTERROR=TRUE ----- Original Message ----- From: "Jeff Bohmer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 11, 2003 11:26 AM Subject: Re: Witango-Talk: Urgent - IIS times out before WiTango is finished This sounds like a client error. There is a setting for clients.ini called CLIENTIOTIMEOUT. It defaults to 300 seconds. If the client doesn't get a response back within CLIENTIOTIMEOUT, it makes the web server return a 500 error. If you have changed QUERYTIMEOUT to 900, try changing CLIENTIOTIMEOUT to 900. Or even 910, so that when something does timeout, you'll be sure the TIMEOUTHTML file is returned instead of the Witango client's 500 error. This CLIENTIOTIMEOUT setting can go under each of your WITANGO_SERVER lines in clients.ini. Also, be careful editing clients.ini -- it is re-read by the Witango client on each request. So don't save that file unless it's in valid format. Otherwise, the client might not process incoming requests. - Jeff >We're suddenly having a problem where WiTango pages that are waiting >for DBMS query results seem to be timing out before WiTango has a >chance to return the results. > >We have some long-running queries (like 5-7 minutes) and everything >was fine, as long as you waited for the queries to return. Now, I >either get an error code 500 from IIS or a 'Cannot find server or >DNS Error' after 5 minutes. If I trace the WiTango logs I see that >after my browser shows an error WiTango finally does get the DBMS >results and continues processing of the taf file and 'returns' the >results to IIS as normal. But my browser has already shown an error >to me. > >I can't find where there might be a 'timeout' setting in IIS that >would control this. There is a connection timeout setting at 900 >seconds - but my error happened at exactly 300 seconds. > >Any ideas? > >Dave Machin > > >E-Mail. [EMAIL PROTECTED] >Tel. 805.614.0123 x 30 >Address: 3130 Skyway Drive #702 >Santa Maria, CA >93455�������������������������������������������������������������������������S"�P"��'P'N^�� � -����˝�][T��~��K�XZ[\� > �Y</x-charset>� -- Jeff Bohmer VisionLink, Inc. _________________________________ 303.402.0170 www.visionlink.org _________________________________ People. Tools. Change. Community. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ������������������������������������������������������������������������D�T�5T%45$�$S�v�F��GG���wwr�v�F�v��6������Ɨ7B�F
