Hello,
I'm working on a new windows 2008 R2 server with IIS 7.5 and I'm creating a new website that creates data sets based on user selections. Currently when I execute a job that is big the browsers time out. Firefox returns "The Connection has timed out" "The server at ????? is taking too long to respond. IE and Chrome just continuously spin and nothing is changing on the screen. Here are the steps I've taken so far.
1. In Application Pool for my connection I increased Idle time-out to 120 minutes.
2. Within my web.config I added
How can I make the browsers not lose their connection to the web server? Some of the jobs could take over 20 minutes.
Thank you
JerryPosted Jul 6, 2014, 6:21 PM
Thank you so much for your reply.
My process is executed on the server synchronously. The process is running a sas job on linux which is extremely fast. Then I generate some other files on the server that exceeds the 5 minute idle time. The reason I don't think it's the connection is that in Chrome it doesn't error out and i'm running the same job.
Is there a way to keep the browser from being idle? Can I run some check every minute that will keep it alive?
Thank you again so much
Pradeep ShetPosted Jul 5, 2014, 12:27 AM
I guess timeout problem is not with the browser. Your sql execution is getting timeout which in turn returning error in the screen.