Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / July 2007

Tip: Looking for answers? Try searching our database.

Why 90 seconds timeout limit doesn't work?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Morgan Cheng - 25 Jul 2007 02:51 GMT
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
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.
Göran Andersson - 25 Jul 2007 07:25 GMT
> I have one webservice A calling another webserivce B. B is time
> costing and sometimes the response takes more than 160 seconds. A is
[quoted text clipped - 8 lines]
> And, there is no "Server.ScriptTimeout" setting in code. I am curious
> why 90 seconds doesn't work.

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.

Signature

Göran Andersson
_____
http://www.guffa.com

Morgan Cheng - 26 Jul 2007 02:57 GMT
On Jul 25, 2:25 pm, G?ran Andersson <gu...@guffa.com> wrote:
> > I have one webservice A calling another webserivce B. B is time
> > costing and sometimes the response takes more than 160 seconds. A is
[quoted text clipped - 13 lines]
> 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.

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.

> --
> G?ran Andersson
> _____http://www.guffa.com

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.