Home / server / Questions / 197317
Accepted
Ernest Mueller
Asked: 2010-11-03 07:08:30 +0800 CST

IIS7/.NET4 App - How To Prevent Deadlocks?

  • 772

I have a problem .NET 4 app I'm trying to load on my IIS7 server. It has a bug where if it gets hit multiple times while it's trying to come up - either initially or from a recycle - it gets deadlocked permanently.

I'm trying to figure out a way to either prevent traffic from coming to it while it's initializing, or in the worst case make the whole thing "single-threaded" so that it can never get two requests in at the same time. I'm already running just one worker process but that's not doing the trick. Ideas? Thanks...

iis-7 .net

2 Answers

  1. Best Answer

    Sounds like a badly written app. I'm not aware of anything you can really do aside from getting the application source looked at and fixed.

    Do you have access to the source or the developer?

    • 1

  2. I tried adding limits to

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Aspnet.config

    <?xml version="1.0" encoding="UTF-8" ?> <configuration>   <system.web>
    <applicationPool 
        maxConcurrentRequestsPerCPU="1"
        maxConcurrentThreadsPerCPU="0" 
        requestQueueLimit="5000" />   </system.web>
    <runtime>
        <legacyUnhandledExceptionPolicy enabled="false" />
        <legacyImpersonationPolicy enabled="true"/>
        <alwaysFlowImpersonationPolicy enabled="false"/>
        <SymbolReadingPolicy enabled="1" />
        <shadowCopyVerifyByTimestamp enabled="true"/>
    </runtime>
    <startup useLegacyV2RuntimeActivationPolicy="true" /> </configuration>

    Per http://msdn.microsoft.com/en-us/library/dd560842.aspx http://blogs.msdn.com/b/tmarq/archive/2007/07/21/asp-net-thread-usage-on-iis-7-0-and-6-0.aspx

    But it didn't work, it still deadlocked. Tried setting the threads to 1 as well, but then the worker process won't even start.

    • 0