Re: IIS 5 100% CPU troubleshooting tools - IISState?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: WenJun Zhang[msft] (v-wzhang_at_online.microsoft.com)
Date: 02/17/04 

Date: Tue, 17 Feb 2004 03:14:30 GMT

Hello John,

I saw 3 idle threads from the the call stack log:

Thread ID: 55
System Thread ID: ce8
Kernel Time: 0:0:18.828
User Time: 0:0:12.109
Thread Type: ASP
Executing Page:

 # ChildEBP RetAddr
00 1118ebcc 7c51c163 ntdll!ZwYieldExecution+0xb
01 1118ebd0 1f668af0 KERNEL32!SwitchToThread+0x6
02 1118ebd4 1f668c4c MSDART!SwitchOrSleep+0x6
03 1118ec08 1f67958a MSDART!CReaderWriterLock3::_LockSpin+0xfc
04 1118ec24 1f66a3d8 MSDART!CReaderWriterLock3::_WriteLockSpin+0x3c
05 1118ec44 1f8a5c06 MSDART!CReaderWriterLock3::WriteLock+0x7a
06 1118ec80 1f8a59bf oledb32!CDCMPoolManager::DrawResource+0xb7
07 1118ece0 1f441756 oledb32!CDPO::Initialize+0x136
08 1118edd0 1f4416e1 msado15!_ConnectAsync+0x96
09 1118ede0 1f441627 msado15!ConnectAsync+0x1f
0a 1118ef6c 1f44389e msado15!CConnection::Open+0xaf0
0b 1118f1e8 6b614279 msado15!CConnection::Invoke+0xb5c
WARNING: Stack unwind information not available. Following frames may
be
wrong.
0c 1118f244 1f4353c0 vbscript!DllCanUnloadNow+0x8e24
0d 00000003 00000000 msado15!ATL::AtlInternalQueryInterface+0x57

Thread ID: 56
System Thread ID: d3c
Kernel Time: 0:0:19.203
User Time: 0:0:10.718
Thread Type: Idle ASP thread
 # ChildEBP RetAddr
00 111cf5f0 7c51c163 ntdll!ZwYieldExecution+0xb
01 111cf5f4 1f668af0 KERNEL32!SwitchToThread+0x6
02 111cf5f8 1f668c4c MSDART!SwitchOrSleep+0x6
03 111cf62c 1f668241 MSDART!CReaderWriterLock3::_LockSpin+0xfc
04 111cf64c 1f8a5aae MSDART!CReaderWriterLock3::ReadLock+0x3b
05 111cf688 1f8a59bf oledb32!CDCMPoolManager::DrawResource+0x82
06 111cf6e8 1f441756 oledb32!CDPO::Initialize+0x136
07 111cf7d8 1f4416e1 msado15!_ConnectAsync+0x96
08 111cf7e8 1f441627 msado15!ConnectAsync+0x1f
09 111cf974 1f732872 msado15!CConnection::Open+0xaf0
0a 111cf9e4 1f384e7f msdfmap!CHandler::OpenConnection+0xf9
0b 111cfa28 1f386a7e msadcf!CDataGramFactory::GetConnection+0x63
0c 111cfa94 1f3860c6 msadcf!CDataGramFactory::Execute+0x15a
0d 111cfbbc 1f3d37d5 msadcf!CDataGramFactory::Invoke+0x410
0e 111cfbec 1f3d3d8c msadcs!CSoapStub::InvokeMethod+0x37
0f 111cfc6c 1f3d3e88 msadcs!CSoapStub::HttpExtensionProc+0x95
10 111cfcc8 787c2b7a msadcs!CSoapAsyncRequest::OnCall+0x6c
11 111cfcd0 77aa1dc5 COMSVCS!STAActivityWorkHelper+0xa
12 111cfd14 77aa1be9 ole32!EnterForCallback+0x6a
13 111cfe40 77aa1aac ole32!SwitchForCallback+0x12b
14 111cfe68 77aa64f4 ole32!PerformCallback+0x50
15 111cfed4 77aa634d
ole32!CObjectContext::InternalContextCallback+0x10d
16 111cfef4 787bfb93 ole32!CObjectContext::DoCallback+0x1a
17 111cff24 787c1d42 COMSVCS!STAActivityWork::DoWork+0x73
18 111cffb4 7c4e987c COMSVCS!STAThread::STAThreadWorker+0x44a
19 111cffec 00000000 KERNEL32!BaseThreadStart+0x52

Thread ID: 59
System Thread ID: 7bc
Kernel Time: 0:0:17.843
User Time: 0:0:10.640
Thread Type: ASP
Executing Page:
E:\WEBS\S0208091\HILBORNINJECTION.COM\WEBROOT\PRODUCT.ASP

 # ChildEBP RetAddr
00 1129ebe8 7c51c163 ntdll!ZwYieldExecution+0xb
01 1129ebec 1f668af0 KERNEL32!SwitchToThread+0x6
02 1129ebf0 1f668c4c MSDART!SwitchOrSleep+0x6
03 1129ec24 1f668241 MSDART!CReaderWriterLock3::_LockSpin+0xfc
04 1129ec44 1f8a5aae MSDART!CReaderWriterLock3::ReadLock+0x3b
05 1129ec80 1f8a59bf oledb32!CDCMPoolManager::DrawResource+0x82
06 1129ece0 1f441756 oledb32!CDPO::Initialize+0x136
07 1129edd0 1f4416e1 msado15!_ConnectAsync+0x96
08 1129ede0 1f441627 msado15!ConnectAsync+0x1f
09 1129ef6c 1f44389e msado15!CConnection::Open+0xaf0
0a 1129f1e8 6b614279 msado15!CConnection::Invoke+0xb5c
WARNING: Stack unwind information not available. Following frames may
be
wrong.
0b 1129f21c 6b60d177 vbscript!DllCanUnloadNow+0x8e24
0c 00000001 00000000 vbscript!DllCanUnloadNow+0x1d22

All of them were pending on oledb's ReaderWriterLock. I think
probably the issue you met is just one listed in the following
article:
FIX: Performance Improvements for OLE DB Session Pooling
http://support.microsoft.com/?id=319982

Accoring to this KB, you can update MDAC version or apply MDAC
service pack to test if they are able to this 100% cpu symptom.

Let us know how the thing is going. Our pleasure to be of assistance.
Have a nice day,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

Relevant Pages

  • IIS Constantly Crashing
    ... User Time: 0:0:0.0 ... Thread Type: Other ... # ChildEBP RetAddr ... Kernel Time: 0:0:0.0 ...
    (microsoft.public.inetserver.iis)
  • Iisstate dump inetinfo CPU 100 %
    ... Kernel Time: 0:0:0.30 ... User Time: 0:0:0.0 ... Thread Type: Other ... # ChildEBP RetAddr ...
    (microsoft.public.inetserver.iis)
  • Re: Application Pool crashes
    ... Kernel Time: 0:0:3.453 ... # ChildEBP RetAddr ... User Time: 0:0:0.31 ... Thread Type: HTTP Compression Thread ...
    (microsoft.public.inetserver.iis)
  • Re: Application Pool crashes
    ... Kernel Time: 0:0:3.453 ... # ChildEBP RetAddr ... User Time: 0:0:0.31 ... Thread Type: HTTP Compression Thread ...
    (microsoft.public.inetserver.iis)
  • Re: IIS 6 Locks Up, Must Restart, No Event Errors
    ... Kernel Time: 0:0:0.0 ... Thread Type: HTTP Compression Thread ... # ChildEBP RetAddr ... User Time: 0:0:0.0 ...
    (microsoft.public.inetserver.iis)