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
Eklavya GuptaPosted Jul 3, 2014, 5:15 PM
SqlCommand command = new SqlCommand();
command.CommandTimeout =
ConfigurationSettings.AppSettings["commandTimeout"];
You can use Appsettings to make your command timeout configurable.
In my view, You should revisit your architecture. Generally Websites are used for making a quick server round trip. Running a long process on the server will make your browser unresponsive and even a small connection fluctuation will abort the process. In my opinion use the website to start a process (maybe a Windows service) on Server. The service will do the required job and update the status in a table. From the browser you can make intermittent calls to the table to know the status of the job.