Yes, I did fix some other reporting issues with a 'push' and a little progress bar - but now I have one where it's just one single query and I have to wait for it to return. The CLIENTIOTIMEOUT thing sounds promising - maybe that's my issue.
----- Original Message ----- From: "Scott Cadillac" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 11, 2003 11:51 AM Subject: RE: Witango-Talk: Urgent - IIS times out before WiTango is finished Hi Dave, It can be deceiving, but your browser probably timeout long before IIS did. This is where you're programming has to get creative. One suggestion is to investigate the "Push" feature of the Search Action. If you're got a long running Loop of some sort, then you can "Push" small bits of content on each Loop to create a continuous stream to the browser until the query finishes. As long as the browser is receiving content in small bits in reasonable intervals - the browser will wait forever without timing out. If your query is in one action, then look at ways of breaking it up. This is just one suggestion - more details from you might trigger some other thoughts.... Hope this helps. Cheers..... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xmlx.ca 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- > -----Original Message----- > From: Dave Machin [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 11, 2003 12:17 PM > To: [EMAIL PROTECTED] > Subject: Witango-Talk: Urgent - IIS times out before WiTango > is finished > > > 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________________________________________________TOUNUBCRB > E G t htp//wwwiano.ommallstta > ________________________________________________________________________ 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
