I guessed that the ASP.NET ExecutionTimeout would have an effect on my IIS-hosted WCF service, however, it does not.
Is there some magic going on in WCF which disables the ExecutionTimeout?
I guessed that the ASP.NET ExecutionTimeout would have an effect on my IIS-hosted WCF service, however, it does not.
Is there some magic going on in WCF which disables the ExecutionTimeout?
milope
On
To my knowledge, ASP.NET and WCF are handled by different handlers. 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. It problably has no effect on anything that is not handled by the ASP.NET handlers (e.g.: Static files).
Copyright © 2021 Jogjafile Inc.
I've found out that since .NET 3.0 SP1 WCF disables ASP.NET's
ExecutionTimeoutby setting the timeout to an infinite value. Therefore, only WCF-specific timeouts apply.