| Author |
Debug Diag report analysis
|
|
|
| Can anyone tell me what is happening in the dump below? Looks like most of
the threads are just waiting but Thread 16??
(Thanks Pat for your help.)
Report for
w3wp. exe__UpaAppPool__PID__1884__Date__11_22_
2005__Time_02_13_04PM__612__IIS
Hang Dump.dmp
Type of Analysis Performed Hang Analysis
Machine Name UPASERVER
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 2
Process ID 1884
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 5 day(s) 21:54:19
Process Up-Time 0 day(s) 00:00:10
Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread Thread
ID: 16 Total CPU Time: 0 day(s) 00:00:03.234 Entry Point for Thread:
mscorsvr!GetAssemblyMDImport+15172
Thread ID: 0 Total CPU Time: 0 day(s) 00:00:00.281 Entry Point for
Thread: w3wp!wmainCRTStartup
Thread ID: 7 Total CPU Time: 0 day(s) 00:00:00.187 Entry Point for
Thread: w3tp!THREAD_MANAGER::ThreadManagerThread
Thread ID: 19 Total CPU Time: 0 day(s) 00:00:00.15 Entry Point for
Thread: mscorsvr!CoInitializeCor+a77
Thread ID: 18 Total CPU Time: 0 day(s) 00:00:00.15 Entry Point for
Thread: mscorsvr!CoInitializeCor+a77
Thread report
Thread 0 - System ID 1304
Entry point w3wp!wmainCRTStartup
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.171
Time spent in kernel mode 0 Days 0:0:0.109
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
w3dt!WP_CONTEXT::RunMainThreadLoop+10
w3dt!UlAtqStartListen+2d
w3core!W3_SERVER::StartListen+bd
w3core!UlW3Start+26e
w3wp!wmain+22a
w3wp!wmainCRTStartup+12b
kernel32!BaseProcessStart+23
Back to Top
Thread 1 - System ID 2112
Entry point ntdll!EtwpEventPump
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
ntdll!EtwpWaitForMultipleObjectsEx+f7
ntdll!EtwpEventPump+27f
kernel32!BaseThreadStart+34
Back to Top
Thread 2 - System ID 1236
Entry point ntdll!RtlpTimerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
ntdll!RtlpTimerThread+47
kernel32!BaseThreadStart+34
Back to Top
Thread 3 - System ID 3480
Entry point ntdll!RtlpWorkerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
ntdll!RtlpWorkerThread+3d
kernel32!BaseThreadStart+34
Back to Top
Thread 4 - System ID 2432
Create time 12:00:00 AM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!ZwReplyWaitReceivePortEx+c
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+1
98
rpcrt4!RecvLotsaCallsWrapper+d
rpcrt4!BaseCachedThreadRoutine+9d
rpcrt4!ThreadStartRoutine+1b
kernel32!BaseThreadStart+34
Back to Top
Thread 5 - System ID 1248
Entry point ole32!CRpcThreadCache::RpcWorkerThreadEn
try
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
kernel32!Sleep+f
ole32!CROIDTable::WorkerThreadLoop+14
ole32!CRpcThread::WorkerLoop+1e
ole32!_imp__InstallApplication <PERF> (ole32+0x0)
kernel32!BaseThreadStart+34
Back to Top
Thread 6 - System ID 2716
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
w3tp!THREAD_MANAGER::ThreadManagerThread
+39
kernel32!BaseThreadStart+34
Back to Top
Thread 7 - System ID 1432
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.46
Time spent in kernel mode 0 Days 0:0:0.140
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
w3tp!THREAD_MANAGER::ThreadManagerThread
+39
kernel32!BaseThreadStart+34
Back to Top
Thread 8 - System ID 3972
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
w3tp!THREAD_MANAGER::ThreadManagerThread
+39
kernel32!BaseThreadStart+34
Back to Top
Thread 9 - System ID 1500
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
w3tp!THREAD_MANAGER::ThreadManagerThread
+39
kernel32!BaseThreadStart+34
Back to Top
Thread 10 - System ID 2684
Entry point ntdll!RtlpWaitThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
ntdll!RtlpWaitThread+161
kernel32!BaseThreadStart+34
Back to Top
Thread 11 - System ID 2816
Entry point w3core!HTTP_COMPRESSION::CompressionThre
ad
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
w3core!HTTP_COMPRESSION::CompressionThre
ad+126
kernel32!BaseThreadStart+34
Back to Top
Thread 12 - System ID 2856
Entry point rpcrt4!ThreadStartRoutine
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!ZwReplyWaitReceivePortEx+c
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+1
98
rpcrt4!RecvLotsaCallsWrapper+d
rpcrt4!BaseCachedThreadRoutine+9d
rpcrt4!ThreadStartRoutine+1b
kernel32!BaseThreadStart+34
Back to Top
Thread 13 - System ID 3676
Entry point ntdll!RtlpIOWorkerThread
Create time 11/22/2005 2:12:59 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
ntdll!RtlpIOWorkerThread+3f
kernel32!BaseThreadStart+34
Back to Top
Thread 14 - System ID 3456
Entry point mscorsvr!GetAssemblyMDImport+15172
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
mscorsvr!GetAssemblyMDImport+15209
mscorsvr!GetAssemblyMDImport+151b3
kernel32!BaseThreadStart+34
Back to Top
Thread 15 - System ID 408
Entry point mscorsvr!Ordinal76+f4a5
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
kernel32!Sleep+f
mscorsvr!Ordinal76+f4f9
kernel32!BaseThreadStart+34
Back to Top
Thread 16 - System ID 2708
Entry point mscorsvr!GetAssemblyMDImport+15172
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:2.937
Time spent in kernel mode 0 Days 0:0:0.296
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
mscorjit!Compiler::optAssertionAdd+5a7
mscorjit!Compiler::optAssertionPropMain+
40
mscorjit!Compiler::compCompile+c9
mscorjit!Compiler::compCompile+1e8
mscorjit!jitNativeCode+95
mscorjit!CILJit::compileMethod+a2
mscorsvr!Ordinal76+c3f8
mscorsvr!Ordinal76+b52a
mscorsvr!Ordinal76+b9c0
mscorsvr!Ordinal76+706a
mscorsvr!Ordinal76+77e4
1aa2f76
Back to Top
Thread 17 - System ID 2336
Entry point mscorsvr!CoInitializeCor+5ae0
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
kernel32!WaitForMultipleObjects+18
mscorsvr!CoInitializeCor+43ad
mscorsvr!CoInitializeCor+4324
kernel32!BaseThreadStart+34
Back to Top
Thread 18 - System ID 2348
Entry point mscorsvr!CoInitializeCor+a77
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.15
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!GetAssemblyMDImport+15d97
mscorsvr!CoInitializeCor+a96
kernel32!BaseThreadStart+34
Back to Top
Thread 19 - System ID 2868
Entry point mscorsvr!CoInitializeCor+a77
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:0.15
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!GetAssemblyMDImport+15d97
mscorsvr!CoInitializeCor+a96
kernel32!BaseThreadStart+34
Back to Top
Thread 20 - System ID 3712
Entry point mscorsvr!CoUninitializeEE+a0fd
Create time 11/22/2005 2:13:00 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
kernel32!WaitForMultipleObjects+18
mscorsvr!CoEEShutDownCOM+2516a
mscorsvr!GetAssemblyMDImport+163db
mscorsvr!CoUninitializeEE+a13e
kernel32!BaseThreadStart+34
Back to Top
Thread 21 - System ID 3800
Entry point mscorsvr!Ordinal76+1c548
Create time 11/22/2005 2:13:01 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
mscorsvr!Ordinal76+1c578
Back to Top
Thread 22 - System ID 2144
Entry point mscorsvr!GetAssemblyMDImport+15172
Create time 11/22/2005 2:13:02 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!GetCompileInfo+1512
mscorsvr!GetAssemblyMDImport+151b3
kernel32!BaseThreadStart+34
Back to Top
HTTP report
IIS ATQ worker thread count 4 Thread(s)
Available ATQ worker thread count 4 Thread(s)
Active client connections 20 client connection(s)
Client Connections
Client connection from 15.62.180.51:3291 to 15.62.180.51:80
Host Header upaserver:80
GET request for /test.aspx
HTTP Version HTTP/1.1
SSL Request False
Time alive 0 day(s) 00:00:15
QueryString
Request mapped to
HTTP Request State HTR_READING_CLIENT_REQUEST
Native Request State NREQ_STATE_PROCESS
19 connection(s) waiting for the next request.
| |
| Pat [MSFT] 2005-11-28, 6:04 pm |
| Looks like a page is getting compiled - which is blocking until the
compilation is completed.
Pat
"Mike" <Mike@discussions.microsoft.com> wrote in message
news:E7A97E11-26C0-4D55-997F-8C6800CD4DF0@microsoft.com...
> Can anyone tell me what is happening in the dump below? Looks like most of
> the threads are just waiting but Thread 16??
>
> (Thanks Pat for your help.)
>
> Report for
> w3wp. exe__UpaAppPool__PID__1884__Date__11_22_
2005__Time_02_13_04PM__612__IIS
> Hang Dump.dmp
> Type of Analysis Performed Hang Analysis
> Machine Name UPASERVER
> Operating System Windows Server 2003 Service Pack 1
> Number Of Processors 2
> Process ID 1884
> Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
> System Up-Time 5 day(s) 21:54:19
> Process Up-Time 0 day(s) 00:00:10
>
>
>
> Top 5 Threads by CPU time
> Note - Times include both user mode and kernel mode for each thread Thread
> ID: 16 Total CPU Time: 0 day(s) 00:00:03.234 Entry Point for
> Thread:
> mscorsvr!GetAssemblyMDImport+15172
> Thread ID: 0 Total CPU Time: 0 day(s) 00:00:00.281 Entry Point for
> Thread: w3wp!wmainCRTStartup
> Thread ID: 7 Total CPU Time: 0 day(s) 00:00:00.187 Entry Point for
> Thread: w3tp!THREAD_MANAGER::ThreadManagerThread
> Thread ID: 19 Total CPU Time: 0 day(s) 00:00:00.15 Entry Point for
> Thread: mscorsvr!CoInitializeCor+a77
> Thread ID: 18 Total CPU Time: 0 day(s) 00:00:00.15 Entry Point for
> Thread: mscorsvr!CoInitializeCor+a77
>
>
>
>
>
> Thread report
>
> Thread 0 - System ID 1304
> Entry point w3wp!wmainCRTStartup
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.171
> Time spent in kernel mode 0 Days 0:0:0.109
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForSingleObject+c
> kernel32!WaitForSingleObjectEx+ac
> kernel32!WaitForSingleObject+12
> w3dt!WP_CONTEXT::RunMainThreadLoop+10
> w3dt!UlAtqStartListen+2d
> w3core!W3_SERVER::StartListen+bd
> w3core!UlW3Start+26e
> w3wp!wmain+22a
> w3wp!wmainCRTStartup+12b
> kernel32!BaseProcessStart+23
>
>
>
>
> Back to Top
>
>
> Thread 1 - System ID 2112
> Entry point ntdll!EtwpEventPump
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForMultipleObjects+c
> ntdll!EtwpWaitForMultipleObjectsEx+f7
> ntdll!EtwpEventPump+27f
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 2 - System ID 1236
> Entry point ntdll!RtlpTimerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtDelayExecution+c
> ntdll!RtlpTimerThread+47
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 3 - System ID 3480
> Entry point ntdll!RtlpWorkerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtRemoveIoCompletion+c
> ntdll!RtlpWorkerThread+3d
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 4 - System ID 2432
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!ZwReplyWaitReceivePortEx+c
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+1
98
> rpcrt4!RecvLotsaCallsWrapper+d
> rpcrt4!BaseCachedThreadRoutine+9d
> rpcrt4!ThreadStartRoutine+1b
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 5 - System ID 1248
> Entry point ole32!CRpcThreadCache::RpcWorkerThreadEn
try
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtDelayExecution+c
> kernel32!SleepEx+68
> kernel32!Sleep+f
> ole32!CROIDTable::WorkerThreadLoop+14
> ole32!CRpcThread::WorkerLoop+1e
> ole32!_imp__InstallApplication <PERF> (ole32+0x0)
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 6 - System ID 2716
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtRemoveIoCompletion+c
> kernel32!GetQueuedCompletionStatus+29
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
> w3tp!THREAD_MANAGER::ThreadManagerThread
+39
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 7 - System ID 1432
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.46
> Time spent in kernel mode 0 Days 0:0:0.140
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtRemoveIoCompletion+c
> kernel32!GetQueuedCompletionStatus+29
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
> w3tp!THREAD_MANAGER::ThreadManagerThread
+39
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 8 - System ID 3972
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtRemoveIoCompletion+c
> kernel32!GetQueuedCompletionStatus+29
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
> w3tp!THREAD_MANAGER::ThreadManagerThread
+39
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 9 - System ID 1500
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtRemoveIoCompletion+c
> kernel32!GetQueuedCompletionStatus+29
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
33
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+
24
> w3tp!THREAD_MANAGER::ThreadManagerThread
+39
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 10 - System ID 2684
> Entry point ntdll!RtlpWaitThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForMultipleObjects+c
> ntdll!RtlpWaitThread+161
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 11 - System ID 2816
> Entry point w3core!HTTP_COMPRESSION::CompressionThre
ad
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForSingleObject+c
> kernel32!WaitForSingleObjectEx+ac
> kernel32!WaitForSingleObject+12
> w3core!HTTP_COMPRESSION::CompressionThre
ad+126
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 12 - System ID 2856
> Entry point rpcrt4!ThreadStartRoutine
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!ZwReplyWaitReceivePortEx+c
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+1
98
> rpcrt4!RecvLotsaCallsWrapper+d
> rpcrt4!BaseCachedThreadRoutine+9d
> rpcrt4!ThreadStartRoutine+1b
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 13 - System ID 3676
> Entry point ntdll!RtlpIOWorkerThread
> Create time 11/22/2005 2:12:59 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtDelayExecution+c
> ntdll!RtlpIOWorkerThread+3f
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 14 - System ID 3456
> Entry point mscorsvr!GetAssemblyMDImport+15172
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtRemoveIoCompletion+c
> kernel32!GetQueuedCompletionStatus+29
> mscorsvr!GetAssemblyMDImport+15209
> mscorsvr!GetAssemblyMDImport+151b3
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 15 - System ID 408
> Entry point mscorsvr!Ordinal76+f4a5
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtDelayExecution+c
> kernel32!SleepEx+68
> kernel32!Sleep+f
> mscorsvr!Ordinal76+f4f9
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 16 - System ID 2708
> Entry point mscorsvr!GetAssemblyMDImport+15172
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:2.937
> Time spent in kernel mode 0 Days 0:0:0.296
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> mscorjit!Compiler::optAssertionAdd+5a7
> mscorjit!Compiler::optAssertionPropMain+
40
> mscorjit!Compiler::compCompile+c9
> mscorjit!Compiler::compCompile+1e8
> mscorjit!jitNativeCode+95
> mscorjit!CILJit::compileMethod+a2
> mscorsvr!Ordinal76+c3f8
> mscorsvr!Ordinal76+b52a
> mscorsvr!Ordinal76+b9c0
> mscorsvr!Ordinal76+706a
> mscorsvr!Ordinal76+77e4
> 1aa2f76
>
>
>
>
> Back to Top
>
>
> Thread 17 - System ID 2336
> Entry point mscorsvr!CoInitializeCor+5ae0
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForMultipleObjects+c
> kernel32!WaitForMultipleObjectsEx+11a
> kernel32!WaitForMultipleObjects+18
> mscorsvr!CoInitializeCor+43ad
> mscorsvr!CoInitializeCor+4324
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 18 - System ID 2348
> Entry point mscorsvr!CoInitializeCor+a77
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.15
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForSingleObject+c
> kernel32!WaitForSingleObjectEx+ac
> kernel32!WaitForSingleObject+12
> mscorsvr!GetAssemblyMDImport+15d97
> mscorsvr!CoInitializeCor+a96
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 19 - System ID 2868
> Entry point mscorsvr!CoInitializeCor+a77
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:0.15
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForSingleObject+c
> kernel32!WaitForSingleObjectEx+ac
> kernel32!WaitForSingleObject+12
> mscorsvr!GetAssemblyMDImport+15d97
> mscorsvr!CoInitializeCor+a96
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 20 - System ID 3712
> Entry point mscorsvr!CoUninitializeEE+a0fd
> Create time 11/22/2005 2:13:00 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForMultipleObjects+c
> kernel32!WaitForMultipleObjectsEx+11a
> kernel32!WaitForMultipleObjects+18
> mscorsvr!CoEEShutDownCOM+2516a
> mscorsvr!GetAssemblyMDImport+163db
> mscorsvr!CoUninitializeEE+a13e
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
>
> Thread 21 - System ID 3800
> Entry point mscorsvr!Ordinal76+1c548
> Create time 11/22/2005 2:13:01 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtDelayExecution+c
> kernel32!SleepEx+68
> mscorsvr!Ordinal76+1c578
>
>
>
>
> Back to Top
>
>
> Thread 22 - System ID 2144
> Entry point mscorsvr!GetAssemblyMDImport+15172
> Create time 11/22/2005 2:13:02 PM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.0
>
>
>
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
>
>
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!NtWaitForSingleObject+c
> kernel32!WaitForSingleObjectEx+ac
> kernel32!WaitForSingleObject+12
> mscorsvr!GetCompileInfo+1512
> mscorsvr!GetAssemblyMDImport+151b3
> kernel32!BaseThreadStart+34
>
>
>
>
> Back to Top
>
> HTTP report
> IIS ATQ worker thread count 4 Thread(s)
> Available ATQ worker thread count 4 Thread(s)
> Active client connections 20 client connection(s)
>
>
>
> Client Connections
> Client connection from 15.62.180.51:3291 to 15.62.180.51:80
> Host Header upaserver:80
> GET request for /test.aspx
> HTTP Version HTTP/1.1
> SSL Request False
> Time alive 0 day(s) 00:00:15
> QueryString
> Request mapped to
> HTTP Request State HTR_READING_CLIENT_REQUEST
> Native Request State NREQ_STATE_PROCESS
>
>
>
>
> 19 connection(s) waiting for the next request.
| |
|
| Thanks... I was guessing the compilation but how do you know it is being
blocked or the page is blocking.?
"Pat [MSFT]" wrote:
[vbcol=seagreen]
> Looks like a page is getting compiled - which is blocking until the
> compilation is completed.
>
> Pat
>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:E7A97E11-26C0-4D55-997F-8C6800CD4DF0@microsoft.com...
| |
| Pat [MSFT] 2005-11-29, 5:58 pm |
| No other thread is doing any work. And now that you mention it, none of
them have done _any_ work since creation which implies that the process was
just restarted and even the thread doing a compilation has only been running
for 2 seconds.
Pat
"Mike" <Mike@discussions.microsoft.com> wrote in message
news:D64DAABE-9DB1-40CD-A4E8-18E115E3729E@microsoft.com...[vbcol=seagreen]
> Thanks... I was guessing the compilation but how do you know it is being
> blocked or the page is blocking.?
>
> "Pat [MSFT]" wrote:
>
|
|
|
|