简体   繁体   English

ASP.NET ExecutionTimeout对IIS托管的WCF服务无效

[英]ASP.NET ExecutionTimeout no effect on IIS-hosted WCF service

I guessed that the ASP.NET ExecutionTimeout would have an effect on my IIS-hosted WCF service, however, it does not. 我猜想ASP.NET ExecutionTimeout会对我的IIS托管的WCF服务产生影响,但是没有。

Is there some magic going on in WCF which disables the ExecutionTimeout? WCF中是否发生了一些魔术,这会禁用ExecutionTimeout?

To my knowledge, ASP.NET and WCF are handled by different handlers. 据我所知,ASP.NET和WCF由不同的处理程序处理。 Being that ASP.NET and WCF are handled differently and the fact that the executionTimeout is within the child elements of system.web (ASP.NET) and not system.serviceModel (WCF) is probably why it has no effect on WCF calls. 由于ASP.NET和WCF的处理方式不同,而executeTimeout在system.web(ASP.NET)的子元素内,而不在system.serviceModel(WCF)的子元素内,因此可能对WCF调用没有影响。 It problably has no effect on anything that is not handled by the ASP.NET handlers (eg: Static files). 它可能对ASP.NET处理程序未处理的任何内容(例如:静态文件)没有影响。

I've found out that since .NET 3.0 SP1 WCF disables ASP.NET's ExecutionTimeout by setting the timeout to an infinite value. 我发现自.NET 3.0 SP1起,WCF通过将超时设置为无限值来禁用ASP.NET的ExecutionTimeout Therefore, only WCF-specific timeouts apply. 因此,仅适用于WCF特定的超时。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM