« Previous Next »

Thread: DefaultAppPool causing 100% CPU

Last post 10-23-2009 1:50 PM by Koski. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 10-23-2009, 11:32 AM

    • Koski
    • Not Ranked
    • Joined on 10-23-2009, 3:26 PM
    • Posts 2

    DefaultAppPool causing 100% CPU

     Hi all,

     We currently run a Win2k3 server with IIS 6.

    There are approximately 175 sites on this particular box, most of them ASP.NET. We have them divided into a number of containers to make recompiles more manageable. Since this morning we've had one instance of w3wp.exe which is keeping CPU pinned at 100%. I've run iisapp.vbs and narrowed it down to the DefaultAppPool. Queued connections are also climbing and sites are extremely slow to load (seemingly regardless of which container they are in). 

     Any ideas would be hugely appreciated.

     

  • 10-23-2009, 1:14 PM In reply to

    • tomkmvp
    • Top 10 Contributor
    • Joined on 03-20-2003, 10:27 AM
    • Central NJ
    • Posts 6,222

    Re: DefaultAppPool causing 100% CPU

  • 10-23-2009, 1:50 PM In reply to

    • Koski
    • Not Ranked
    • Joined on 10-23-2009, 3:26 PM
    • Posts 2

    Re: DefaultAppPool causing 100% CPU

     Very few, but we've found that the w3wp.exe instance for DefaultAppPool was only spiking CPU because it accounts for the queued connections. Turns out this was a by-product of the real issue, which seems to be code on one specific site which is deadlocking SQL connections and maxing out the TCP stack. If that one site is taken down, the queued connections and CPU usage return to normal.

    Thanks for the help though! Dev team is looking into rolling back the updates now until we can figure out the problem with the new code.

Page 1 of 1 (3 items)
Microsoft Communities