Problem with lengthy process

[atefshehata]

hi all,


i'm using iis6 installed on win2003 , dotnet framework 1.1 .


My problem is..
a page on my application have a lengthy process which takes about 4
minutes (performing database transactions ..) to completes.


user click on the transaction button to start this lengthy process.


after about 140 seconds the client browser displays the error message
'page can't displayed ...'.


note> the transactions continues to work untill it finish !


so the client can't see the results of the executed transactions.


on iis i set connectiontimeout=900.
on code i set server.scripttimeout=900 .
on web.config. i set <httpRuntime executionTimeout="900" ...>
and the sqlcommand.commandtimeout=180.


i don't know what is wrong,why the client browser timed-out every time
?


thanks for any help .


atef

 

[Guest]

Assume this is database? If so, check both connection and command time outs.


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[atefshehata]

Assume this is database? If so, check both connection and command

time outs.

first thanks for your reply.

No , the database transactions is not the reason, because the
transactions completes successfully even after the client timed-out.

However i re-checked the connection timeout and command timeout
connection timeout is 20 and command timeout is 180

important notes found by further tests...
the scenario mentioned in my first message done through the internet.
eg.)i tested this lengthy process on the production site from my office

and the production site behinds a firewall .

on the development site(local zone) every thing is ok !!!!!
when i test the production site from its local zone , it works too !

do you think the firewall is the cause ?
in other words , do you think the firewall can disconnects the client
connection if it is idle for some time ?

i asked the network administrator of the production site and he said no
..

any help please .

thanks

atef

 

[Nick Malik [Microsoft]]

four minutes is a long time.

Why not fire off a process using .Net Remoting that will run in the
background, and return the web page with a timer to autoupdate every 10
seconds. Then the web browser can poll a page with params that allow you to
query the progress of the background process. When the background process
completes, redirect to the next page where you can show results.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.

 

[atef shehata]

Thanks Nick for your reply

I statrted to use threading to overcome this problem.

But i still needs to know how to configure IIS to not disconnects the
client