Thanks, I have added the default entry of 300 in the client.ini as a reminder I searched all the latest docs I could find and didn't see it.
Ben Johansen - http://www.pcforge.com Authorized Witango & MDaemon Reseller Available for Witango Developement -----Original Message----- From: Jeff Bohmer [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2003 11:52 AM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: Urgent - IIS times out before WiTango is finished I reported "the client giving up after 300 seconds" as a bug to With. Then they told me about CLIENTIOTIMEOUT. At the time, this wasn't in any documentation that I could find. I'm not sure if the docs have it yet. I don't know of any other undocumented stuff. Any other clients.ini entries I know about are outlined in the Pro Config Guide and only apply to the Professional app server. - Jeff >Wow, where did you find out about this great nugget of information? >Is there anymore? > >Ben Johansen - http://www.pcforge.com >Authorized Witango & MDaemon Reseller >Available for Witango Developement > > >-----Original Message----- >From: Jeff Bohmer [mailto:[EMAIL PROTECTED] >Sent: Thursday, September 11, 2003 11:26 AM >To: [EMAIL PROTECTED] >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��� � >-����˝�][��˘��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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
