Why 90 seconds timeout limit doesn't work?

  • Thread starter Thread starter Morgan Cheng
  • Start date Start date
M

Morgan Cheng

I have one webservice A calling another webserivce B. B is time
costing and sometimes the response takes more than 160 seconds. A is
supposed to be Thread.Abort in 90 seconds. However, the 90 seconds
time limit doesn't work. It only get "The operation has timed out"
WebException from calling B afte 100 seconds.

I checked IIS6 Manager, Properties->Home Directory->Configuration-
Options. The ASP script timeout is 90 seconds as default. The
Click to expand...
webservice is written in C#. Does it matter?

And, there is no "Server.ScriptTimeout" setting in code. I am curious
why 90 seconds doesn't work.
 
Morgan said:
I have one webservice A calling another webserivce B. B is time
costing and sometimes the response takes more than 160 seconds. A is
supposed to be Thread.Abort in 90 seconds. However, the 90 seconds
time limit doesn't work. It only get "The operation has timed out"
WebException from calling B afte 100 seconds.

I checked IIS6 Manager, Properties->Home Directory->Configuration-
webservice is written in C#. Does it matter?

And, there is no "Server.ScriptTimeout" setting in code. I am curious
why 90 seconds doesn't work.
Click to expand...

How are you doing the Thread.Abort?

If you expect the ASP script timeout to do that, your expectations are
not realistic, as it is not an ASP script that you are running.
 
How are you doing the Thread.Abort?

If you expect the ASP script timeout to do that, your expectations are
not realistic, as it is not an ASP script that you are running.
Click to expand...

For ThreadAbortException, I am going to catch it and log a error. Then
call Thread.ResetAbort() to prevent it from rethrow.

I don't want to change the default timeout value. Just curious which
config actually control the timeout of webservice.
 
Back
Top