RE: Long running web service call ends with ThreadAbortException
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Mon, 21 Jan 2008 09:35:29 GMT
Hi Mads,
Have you got any progress on this issue? If there is anything else we can
help, welcome to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
Organization: Microsoft
Date: Wed, 16 Jan 2008 03:13:01 GMT
Subject: RE: Long running web service call ends with ThreadAbortException
the
Thanks for your reply Mads,
I'm sorry to hear that. Yes, the httpruntime executionTimeout is a common
issue. As you said enlarge the timeout not work, have you verified that
server webservice's <compilation debug ...> as been set to "false"(theuse
executionTimeout setting is ignored under debug mode)
Also, whether some other code in the service call that will raise timeout
errror? You can try creating a simplified webservice method(which just
Thread.Sleep to simulate a long run task) and call it in client to seejust
whether it will result to the same error behavior.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: =?Utf-8?B?TWFkcyBOaWVsc2Vu?= <ResultmakerMSDN@xxxxxxxxxxxxxxxxx>
Subject: RE: Long running web service call ends with ThreadAbortException
Date: Sun, 13 Jan 2008 23:11:00 -0800
my
Thanks for replying; unfortunately your solution does not alleviate the
problem. I have tried using the ExecutionTimeout attribute before during
search for a solution, but tried once more, after reading your reply,
to"ThreadAbortException"
be sure, and I still get the ThreadAbortException.the
I have tried to do remote debugging of the web service in order to find
part where it breaks down, but (sadly) the problem goes away while doingso.
"Steven Cheng[MSFT]" wrote:
Hi Mads,
From your description, I understand you often get
inserver-side
your .NET client app which calls some long-run server-side webservice,
correct?
Based on my experience, such problem is likely caused by the
service method exceed the runtime execution timeout scope. If you can
reach and adjust the server-side service, I suggest you try enlarge the
"executionTimeout" in <httpRuntime> setting to see whether it helps:
#httpRuntime Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-us/library/e1f13641.aspx
Here is a former thread that also discussing on this:
#ThreadAbortException & executionTimeout
http://www.thescripts.com/forum/thread467787.html
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
.
- References:
- RE: Long running web service call ends with ThreadAbortException
- From: Steven Cheng[MSFT]
- RE: Long running web service call ends with ThreadAbortException
- From: Mads Nielsen
- RE: Long running web service call ends with ThreadAbortException
- From: Steven Cheng[MSFT]
- RE: Long running web service call ends with ThreadAbortException
- Prev by Date: Re: \r\n Problem
- Next by Date: Re: \r\n Problem
- Previous by thread: RE: Long running web service call ends with ThreadAbortException
- Next by thread: Passing time, date and timezone
- Index(es):
Relevant Pages
|