Perhaps asnyc mode or BizTalk would be of help?
- Adwait
--
Adwait Ullal
e: mailto:***@gmail.com
w: http://www.adwait.com
l: http://www.linkedin.com/in/adwait
j: http://finance.groups.yahoo.com/group/AdwaitsDotNetJobs
On 5/16/07, Shawn Wildermuth (MVP) <***@adoguy.com> wrote:
>
> Ummmm....to ask the obvious question, why do you have a webservice that
> runs
> over 3 hours?
>
> Thanks,
>
> Shawn Wildermuth
> http://adoguy.com
> http://wildermuthconsulting.com
> Microsoft MVP (C#), MCSD.NET, Author and Speaker
>
>
> -----Original Message-----
> From: Discussion of building .NET applications targeted for the Web
> [mailto:DOTNET-***@DISCUSS.DEVELOP.COM] On Behalf Of Ainsley, Robert, ISD
> Sent: Wednesday, May 16, 2007 5:07 PM
> To: DOTNET-***@DISCUSS.DEVELOP.COM
> Subject: [DOTNET-WEB] WebService method timing out after exactly 3:00
> hours
>
> I've got a console application that invokes a synchronous webservice
> method multiple times. Whenever the method takes more than 3 hours to
> execute, the console application dies with the following error:
>
> The request failed with the error message:
> --
> Request timed out.
> Server Error in '/SPAExecuteEngine' Application.
> Request timed out.
>
> Description:
> An unhandled exception occurred during the execution of the current web
> request. Please review the
> stack trace for more information about the error and where it
> originated in the code.
>
> Exception Details:
> System.Web.HttpException: Request timed out.
>
> Source Error:
> An unhandled exception was generated during the execution of the current
> web request. Information regarding the origin and location
> of the exception can be identified using the exception stack trace
> below.
>
> Stack Trace:
>
> HttpException (0x80004005): Request timed out.
>
> Version Information:
> Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
> Version:2.0.50727.42
>
> [HttpException]: Request timed out.
> at SecuritizationUpdate.MainModule.Main() in
> C:SecuritizationUpdate\MainModule.vb:line 74
>
> =======================================================
>
>
> The error log entry for the web service is:
>
> Event Type: Error
> Event Source: XXX
> Event Category: None
> Event ID: 0
> Date: 5/16/2007
> Time: 2:37:01 PM
> User: N/A
> Computer: XXX
> Description:
>
> General Information
> *********************************************
> Additional Info:
> ExceptionManager.MachineName: XXX
> ExceptionManager.TimeStamp: 5/16/2007 2:37:01 PM
> ExceptionManager.FullName:
> Microsoft.ApplicationBlocks.ExceptionManagement, Version=1.0.1522.17033,
> Culture=neutral, PublicKeyToken=null
> ExceptionManager.AppDomainName:
> /LM/W3SVC/10/Root/SPAExecuteEngine-1-128237812591142484
> ExceptionManager.ThreadIdentity: NT AUTHORITY\NETWORK SERVICE
> ExceptionManager.WindowsIdentity: XXX
>
> 1) Exception Information
> *********************************************
> Exception Type: System.Exception
> Message: Error Executing Securitization Id 24.
> Data: System.Collections.ListDictionaryInternal
> TargetSite: NULL
> HelpLink: NULL
> Source: NULL
>
> 2) Exception Information
> *********************************************
> Exception Type: System.Threading.ThreadAbortException
> ExceptionState: System.Web.HttpApplication+CancelModuleException
> Message: Thread was being aborted.
> Data: System.Collections.ListDictionaryInternal
> TargetSite: Void Update(System.Data.SqlClient.SqlTransaction)
> HelpLink: NULL
> Source: XXX
>
> StackTrace Information
> *********************************************
> <Deleted for security.>
>
>
> ==================================================================
>
> The webservice .Timeout parameter in the console application is set to
> 36,000,000 milliseconds, which should be 10 hours.
>
> In the webservice web.config, httpRuntime executionTimeout="10800", is
> three hours. Thinking that might be it, I set it to 1 second and ran
> iisreset. I invoked the method with data that should take 20 seconds to
> run. It ran to completion without any error in approximately 20 seconds.
>
> I also invoked the method asynchronously with .BeginMethod and
> Nothing/null for the callback parameters. The webservice method died at
> exactly 3 hours with the same ThreadAbortException as above.
>
> Is httpRuntime executionTimeout="10800" really the source of my problem
> and I messed up trying to change the setting?
>
> Is there some other setting I'm missing that I need to change?
>
> Is there a 3 hour limit hard-coded somewhere that I can't change?
>
> Thanks!
>
>
>
>
> ****************************************************************************
> *
> If you are not the intended recipient of this e-mail, please notify
> the sender immediately. The contents of this e-mail do not amend
> any existing disclosures or agreements unless expressly stated.
>
> ****************************************************************************
> *
>
> ===================================
> This list is hosted by DevelopMentor. http://www.develop.com
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com
>
> ===================================
> This list is hosted by DevelopMentor(r) http://www.develop.com
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com
>
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com