RE: Problem with Browser Refresh - the solution

[Katie]

Yup, thank you David!  This was the issue!  The problem has been solved, but I sort of wish it wasn't browser specific, cuz now I may have to have several clients check their registry which is always dangerous.

I already had a value of 30000 populated in my pre-existing RECEIVETIMEOUT dword, so it's no wonder it was always timing out after 30 seconds.  I wonder how/when this dword got populated?  I've checked a few other clients randomly and they had NO RECEIVETIMEOUT dword, and they did not have a browser timeout issue like I was having.

Thanks to everyone else who offered a suggestion as well.  I really appreciate it!  :-D

-Katie
www.Planet-K.com

---

From: "Lewis, David" <[EMAIL PROTECTED]>
Sent: Friday, November 19, 2004 7:22 AM
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: Problem with Browser Refresh (DFWCFUG)

I thought the default browser wait time was 5 minutes -- sounds like the browser is not the issue..but, i was researching this for something else and while I have not tried it yet, here is a post that may help with the browser timeout setting in the registry.

 

http://groups.google.com/groups?hl=en&lr=&selm=AV9P5.42364%24e5.54497%40newsfeeds.bigpond.com

 

-David

-----Original Message-----
From: Katie [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 3:43 PM
To: [EMAIL PROTECTED]
Subject: Problem with Browser Refresh (DFWCFUG)

Hello! 

Boy, I hope someone out there can help me!  We are just STUMPED on this issue!  OK, here's the problem...

We have an internal application running on CF 5.0 that has a web browser front end.  We use IE 6.0 and IIS 5.0.

The problem is, when hitting submit, some of our queries take longer than 30 seconds to complete.  And unfortunately, the web browser page load is timing out in 30 seconds no matter whether the query has returned results to the web page or not.  So we keep getting a lot of  "Page cannot be Displayed" errors.  Please note that the query itself *IS* completing, but the web page is not able to return the results within the 30 seconds.

This really has nothing to do with the timeout of the query, like I explained.  We've played with the RequestTimeout URL var, the timeout attribute on the CFQuery and the CFAdmin server-wide timeout, and CFFLUSH, but none of those affect the length of time the browser page itself must receive results within.  The CFFLUSH won't process until after a query has completed, so if the query takes longer than 30 seconds, the CFFLUSH has no effect.

HOW CAN WE EXTEND THE LENGTH OF THE BROWSER WEB PAGE LOAD TIME? 30 seconds is not long enough.  We've searched the web high and low and cannot find anything on how to do this.  SURELY someone out there has web browser queries that take longer than 30 seconds to complete and has found a solution to this problem.  If so, please share, I'd be forever grateful!   :-)

-Katie