 |
|
|
|
Next: Google ads query
|
| Author |
Message |
External
Since: Dec 16, 2004
Posts: 10
|
(Msg. 1) Posted: Fri Dec 17, 2004 6:09 am
Post subject: 2003 Server, quad proc, IIS box - CPU @100%
Archived from groups: microsoft>public>inetserver>iis (more info?)
|
|
|
Our support group finally got the customer site to fail with high machine CPU
and w3wp.exe running between 70 - 99% of the total cpu. The following
IISSTATE log shows a number of threads down in sx32w [which I believe belongs
to Globetrotter's FlexLM hardware dongle license]. Does anyone have any
experience with the FlexLM hardware dongles in a multi-processor IIS
environment? Also, why does it appear that all some of the thread stacks
have mscorsvr in them - isn't this the core CLR engine?
NOTE: I am only posted the threads that reference the sx32w DLL in their
stack because I can't post the log because of the 30000 char limit. If there
is another way to post the entire log, please let me know!
Opened log file 'C:\iisstate\output\IISState-2716.log'
***********************
Starting new log output
IISState version 3.3.1
Fri Dec 17 06:48:15 2004
OS = Windows 2003 Server
Executable: w3wp.exe
PID = 2716
Note: Thread times are formatted as HH:MM:SS.ms
***********************
Thread ID: 19
System Thread ID: e48
Kernel Time: 0:14:58.703
User Time: 0:0:16.125
*** WARNING: Unable to verify checksum for C:\WINDOWS\system32\sx32w.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\sx32w.dll -
Thread Type: Other
# ChildEBP RetAddr
00 0466f790 77f4303b SharedUserData!SystemCallStub+0x4
01 0466f794 77e4905d ntdll!NtReadFile+0xc
02 0466f7fc 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0466f94c 0da0223c sx32w!Ordinal19+0x6671
04 0466f9a0 0d956862 0xda0223c
05 0466f9ec 0d95672b 0xd956862
06 0466fa44 07f39938 0xd95672b
07 0466fad4 7921ab56 0x7f39938
08 0466fb14 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
09 0466fb5c 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
0a 0466fbc4 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
0b 0466fca8 791b4c26 0x472a179
0c 0466fcd4 791b4c7e mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
*,0>,0>::FindItem+0x1b
0d 0466fce4 791b4c8d mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
*,0>,0>::FindItem+0xe
0e 0466fcf0 791b48cd mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
*,0>,0>::GetValue+0xb
0f 0466fd10 791b4d2f mscorsvr!Thread::SetStaticData+0x5c
10 0466fd70 0466fd98 mscorsvr!Thread::SafeSetStaticData+0x63
11 00000000 00000000 0x466fd98
Thread ID: 27
System Thread ID: 890
Kernel Time: 0:13:5.468
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0dcffb1c 77f4303b SharedUserData!SystemCallStub+0x4
01 0dcffb20 77e4905d ntdll!NtReadFile+0xc
02 0dcffb88 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0dcffc5c 10400000 sx32w!Ordinal19+0x6671
04 10400010 50030690 0x10400000
05 00000011 00000000 0x50030690
Thread ID: 36
System Thread ID: be4
Kernel Time: 0:4:36.687
User Time: 0:0:0.484
Thread Type: Other
# ChildEBP RetAddr
00 0e3af868 77f4303b SharedUserData!SystemCallStub+0x4
01 0e3af86c 77e4905d ntdll!NtReadFile+0xc
02 0e3af8d4 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 00000000 00000000 sx32w!Ordinal19+0x6671
Thread ID: 45
System Thread ID: 380
Kernel Time: 0:14:42.546
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0ee1f22c 77f4303b SharedUserData!SystemCallStub+0x4
01 0ee1f230 77e4905d ntdll!NtReadFile+0xc
02 0ee1f298 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0ee1f3cc 0da0223c sx32w!Ordinal19+0x6671
04 0ee1f420 0d956862 0xda0223c
05 0ee1f46c 0d95672b 0xd956862
06 0ee1f4c4 07f39938 0xd95672b
07 0ee1f554 7921ab56 0x7f39938
08 0ee1f594 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
09 0ee1f5dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
0a 0ee1f644 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
0b 0ee1f728 00000000 0x472a179
Thread ID: 49
System Thread ID: b78
Kernel Time: 0:14:43.953
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00aaf02c 77f4303b SharedUserData!SystemCallStub+0x4
01 00aaf030 77e4905d ntdll!NtReadFile+0xc
02 00aaf098 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 00aaf1cc 0da0223c sx32w!Ordinal19+0x6671
04 00aaf220 0d956862 0xda0223c
05 00aaf26c 0d95672b 0xd956862
06 00aaf2c4 07f39938 0xd95672b
07 00aaf354 7921ab56 0x7f39938
08 00aaf394 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
09 00aaf3dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
0a 00aaf444 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
0b 00aaf528 0e0158d0 0x472a179
0c 0e0158d0 00000000 0xe0158d0
Thread ID: 51
System Thread ID: bd4
Kernel Time: 0:14:40.781
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0f05ef2c 77f4303b SharedUserData!SystemCallStub+0x4
01 0f05ef30 77e4905d ntdll!NtReadFile+0xc
02 0f05ef98 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0f05f0cc 0da0223c sx32w!Ordinal19+0x6671
04 0f05f120 0d956862 0xda0223c
05 0f05f16c 0d95672b 0xd956862
06 0f05f1c4 07f39938 0xd95672b
07 0f05f254 7921ab56 0x7f39938
08 0f05f294 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
09 0f05f2dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
0a 0f05f344 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
0b 0f05f428 5900cb38 0x472a179
0c 5900cb38 00000000 0x5900cb38
Thread ID: 52
System Thread ID: 448
Kernel Time: 0:5:1.312
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0f09eeac 77f4303b SharedUserData!SystemCallStub+0x4
01 0f09eeb0 77e4905d ntdll!NtReadFile+0xc
02 0f09ef18 0da56671 kernel32!ReadFile+0x16c
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0f09f04c 0da0223c sx32w!Ordinal19+0x6671
04 0f09f0a0 0d956862 0xda0223c
05 0f09f0ec 0d95672b 0xd956862
06 0f09f144 07f39938 0xd95672b
07 0f09f1d4 7921ab56 0x7f39938
08 0f09f214 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
09 0f09f25c 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
0a 0f09f2c4 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
0b 0f09f3a8 00000000 0x472a179
--
Bob
Sr. Microsoft Architect
Lighthammer Software |
|
| Back to top |
|
 | |
External
Since: Aug 24, 2003
Posts: 1478
|
(Msg. 2) Posted: Fri Dec 17, 2004 6:13 pm
Post subject: Re: 2003 Server, quad proc, IIS box - CPU @100% [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
You are correct about the mscorsvr.dll. That is the multi-processor version
of the CLR Runtime. The single proce is called mscorwks.dll (workstation
version). The biggest difference is in how GC is managed (optimized for
single proc or multi-proc).
Based on the threads posted, I agree with your assessment. Have you
contacted the vendor to see if they have an update?
Pat
"Bob" <bob.TakeThisOut@discussions.microsoft.com> wrote in message
news:FEDD5BB2-5789-482C-B75E-F21DDE654348@microsoft.com...
> Our support group finally got the customer site to fail with high machine
> CPU
> and w3wp.exe running between 70 - 99% of the total cpu. The following
> IISSTATE log shows a number of threads down in sx32w [which I believe
> belongs
> to Globetrotter's FlexLM hardware dongle license]. Does anyone have any
> experience with the FlexLM hardware dongles in a multi-processor IIS
> environment? Also, why does it appear that all some of the thread stacks
> have mscorsvr in them - isn't this the core CLR engine?
>
> NOTE: I am only posted the threads that reference the sx32w DLL in their
> stack because I can't post the log because of the 30000 char limit. If
> there
> is another way to post the entire log, please let me know!
>
> Opened log file 'C:\iisstate\output\IISState-2716.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Fri Dec 17 06:48:15 2004
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 2716
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
> Thread ID: 19
> System Thread ID: e48
> Kernel Time: 0:14:58.703
> User Time: 0:0:16.125
> *** WARNING: Unable to verify checksum for C:\WINDOWS\system32\sx32w.dll
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
> for
> C:\WINDOWS\system32\sx32w.dll -
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0466f790 77f4303b SharedUserData!SystemCallStub+0x4
> 01 0466f794 77e4905d ntdll!NtReadFile+0xc
> 02 0466f7fc 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 0466f94c 0da0223c sx32w!Ordinal19+0x6671
> 04 0466f9a0 0d956862 0xda0223c
> 05 0466f9ec 0d95672b 0xd956862
> 06 0466fa44 07f39938 0xd95672b
> 07 0466fad4 7921ab56 0x7f39938
> 08 0466fb14 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> 09 0466fb5c 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> 0a 0466fbc4 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> 0b 0466fca8 791b4c26 0x472a179
> 0c 0466fcd4 791b4c7e mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
> *,0>,0>::FindItem+0x1b
> 0d 0466fce4 791b4c8d mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
> *,0>,0>::FindItem+0xe
> 0e 0466fcf0 791b48cd mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
> *,0>,0>::GetValue+0xb
> 0f 0466fd10 791b4d2f mscorsvr!Thread::SetStaticData+0x5c
> 10 0466fd70 0466fd98 mscorsvr!Thread::SafeSetStaticData+0x63
> 11 00000000 00000000 0x466fd98
>
>
> Thread ID: 27
> System Thread ID: 890
> Kernel Time: 0:13:5.468
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0dcffb1c 77f4303b SharedUserData!SystemCallStub+0x4
> 01 0dcffb20 77e4905d ntdll!NtReadFile+0xc
> 02 0dcffb88 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 0dcffc5c 10400000 sx32w!Ordinal19+0x6671
> 04 10400010 50030690 0x10400000
> 05 00000011 00000000 0x50030690
>
> Thread ID: 36
> System Thread ID: be4
> Kernel Time: 0:4:36.687
> User Time: 0:0:0.484
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0e3af868 77f4303b SharedUserData!SystemCallStub+0x4
> 01 0e3af86c 77e4905d ntdll!NtReadFile+0xc
> 02 0e3af8d4 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 00000000 00000000 sx32w!Ordinal19+0x6671
>
> Thread ID: 45
> System Thread ID: 380
> Kernel Time: 0:14:42.546
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0ee1f22c 77f4303b SharedUserData!SystemCallStub+0x4
> 01 0ee1f230 77e4905d ntdll!NtReadFile+0xc
> 02 0ee1f298 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 0ee1f3cc 0da0223c sx32w!Ordinal19+0x6671
> 04 0ee1f420 0d956862 0xda0223c
> 05 0ee1f46c 0d95672b 0xd956862
> 06 0ee1f4c4 07f39938 0xd95672b
> 07 0ee1f554 7921ab56 0x7f39938
> 08 0ee1f594 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> 09 0ee1f5dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> 0a 0ee1f644 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> 0b 0ee1f728 00000000 0x472a179
>
> Thread ID: 49
> System Thread ID: b78
> Kernel Time: 0:14:43.953
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00aaf02c 77f4303b SharedUserData!SystemCallStub+0x4
> 01 00aaf030 77e4905d ntdll!NtReadFile+0xc
> 02 00aaf098 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 00aaf1cc 0da0223c sx32w!Ordinal19+0x6671
> 04 00aaf220 0d956862 0xda0223c
> 05 00aaf26c 0d95672b 0xd956862
> 06 00aaf2c4 07f39938 0xd95672b
> 07 00aaf354 7921ab56 0x7f39938
> 08 00aaf394 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> 09 00aaf3dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> 0a 00aaf444 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> 0b 00aaf528 0e0158d0 0x472a179
> 0c 0e0158d0 00000000 0xe0158d0
>
> Thread ID: 51
> System Thread ID: bd4
> Kernel Time: 0:14:40.781
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0f05ef2c 77f4303b SharedUserData!SystemCallStub+0x4
> 01 0f05ef30 77e4905d ntdll!NtReadFile+0xc
> 02 0f05ef98 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 0f05f0cc 0da0223c sx32w!Ordinal19+0x6671
> 04 0f05f120 0d956862 0xda0223c
> 05 0f05f16c 0d95672b 0xd956862
> 06 0f05f1c4 07f39938 0xd95672b
> 07 0f05f254 7921ab56 0x7f39938
> 08 0f05f294 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> 09 0f05f2dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> 0a 0f05f344 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> 0b 0f05f428 5900cb38 0x472a179
> 0c 5900cb38 00000000 0x5900cb38
>
>
>
>
> Thread ID: 52
> System Thread ID: 448
> Kernel Time: 0:5:1.312
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0f09eeac 77f4303b SharedUserData!SystemCallStub+0x4
> 01 0f09eeb0 77e4905d ntdll!NtReadFile+0xc
> 02 0f09ef18 0da56671 kernel32!ReadFile+0x16c
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 0f09f04c 0da0223c sx32w!Ordinal19+0x6671
> 04 0f09f0a0 0d956862 0xda0223c
> 05 0f09f0ec 0d95672b 0xd956862
> 06 0f09f144 07f39938 0xd95672b
> 07 0f09f1d4 7921ab56 0x7f39938
> 08 0f09f214 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> 09 0f09f25c 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> 0a 0f09f2c4 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> 0b 0f09f3a8 00000000 0x472a179
>
> --
> Bob
> Sr. Microsoft Architect
> Lighthammer Software<!-- ~MESSAGE_AFTER~ --> |
|
| Back to top |
|
| |
External
Since: Dec 16, 2004
Posts: 10
|
(Msg. 3) Posted: Sat Dec 18, 2004 4:27 am
Post subject: Re: 2003 Server, quad proc, IIS box - CPU @100% [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
No, I have not contacted the vendor yet. We have a soft-license approach
that can be used for these customers, so we have switched then over to that
and will monitor the situation.
Thanks for your confirmation,
Bob
"Pat [MSFT]" wrote:
> You are correct about the mscorsvr.dll. That is the multi-processor version
> of the CLR Runtime. The single proce is called mscorwks.dll (workstation
> version). The biggest difference is in how GC is managed (optimized for
> single proc or multi-proc).
>
> Based on the threads posted, I agree with your assessment. Have you
> contacted the vendor to see if they have an update?
>
>
> Pat
>
> "Bob" <bob DeleteThis @discussions.microsoft.com> wrote in message
> news:FEDD5BB2-5789-482C-B75E-F21DDE654348@microsoft.com...
> > Our support group finally got the customer site to fail with high machine
> > CPU
> > and w3wp.exe running between 70 - 99% of the total cpu. The following
> > IISSTATE log shows a number of threads down in sx32w [which I believe
> > belongs
> > to Globetrotter's FlexLM hardware dongle license]. Does anyone have any
> > experience with the FlexLM hardware dongles in a multi-processor IIS
> > environment? Also, why does it appear that all some of the thread stacks
> > have mscorsvr in them - isn't this the core CLR engine?
> >
> > NOTE: I am only posted the threads that reference the sx32w DLL in their
> > stack because I can't post the log because of the 30000 char limit. If
> > there
> > is another way to post the entire log, please let me know!
> >
> > Opened log file 'C:\iisstate\output\IISState-2716.log'
> >
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Fri Dec 17 06:48:15 2004
> >
> > OS = Windows 2003 Server
> > Executable: w3wp.exe
> > PID = 2716
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> > Thread ID: 19
> > System Thread ID: e48
> > Kernel Time: 0:14:58.703
> > User Time: 0:0:16.125
> > *** WARNING: Unable to verify checksum for C:\WINDOWS\system32\sx32w.dll
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> > for
> > C:\WINDOWS\system32\sx32w.dll -
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0466f790 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0466f794 77e4905d ntdll!NtReadFile+0xc
> > 02 0466f7fc 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 0466f94c 0da0223c sx32w!Ordinal19+0x6671
> > 04 0466f9a0 0d956862 0xda0223c
> > 05 0466f9ec 0d95672b 0xd956862
> > 06 0466fa44 07f39938 0xd95672b
> > 07 0466fad4 7921ab56 0x7f39938
> > 08 0466fb14 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> > 09 0466fb5c 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> > 0a 0466fbc4 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> > 0b 0466fca8 791b4c26 0x472a179
> > 0c 0466fcd4 791b4c7e mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
> > *,0>,0>::FindItem+0x1b
> > 0d 0466fce4 791b4c8d mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
> > *,0>,0>::FindItem+0xe
> > 0e 0466fcf0 791b48cd mscorsvr!EEHashTable<void *,EEPtrHashTableHelper<void
> > *,0>,0>::GetValue+0xb
> > 0f 0466fd10 791b4d2f mscorsvr!Thread::SetStaticData+0x5c
> > 10 0466fd70 0466fd98 mscorsvr!Thread::SafeSetStaticData+0x63
> > 11 00000000 00000000 0x466fd98
> >
> >
> > Thread ID: 27
> > System Thread ID: 890
> > Kernel Time: 0:13:5.468
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0dcffb1c 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0dcffb20 77e4905d ntdll!NtReadFile+0xc
> > 02 0dcffb88 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 0dcffc5c 10400000 sx32w!Ordinal19+0x6671
> > 04 10400010 50030690 0x10400000
> > 05 00000011 00000000 0x50030690
> >
> > Thread ID: 36
> > System Thread ID: be4
> > Kernel Time: 0:4:36.687
> > User Time: 0:0:0.484
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0e3af868 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0e3af86c 77e4905d ntdll!NtReadFile+0xc
> > 02 0e3af8d4 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 00000000 00000000 sx32w!Ordinal19+0x6671
> >
> > Thread ID: 45
> > System Thread ID: 380
> > Kernel Time: 0:14:42.546
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0ee1f22c 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0ee1f230 77e4905d ntdll!NtReadFile+0xc
> > 02 0ee1f298 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 0ee1f3cc 0da0223c sx32w!Ordinal19+0x6671
> > 04 0ee1f420 0d956862 0xda0223c
> > 05 0ee1f46c 0d95672b 0xd956862
> > 06 0ee1f4c4 07f39938 0xd95672b
> > 07 0ee1f554 7921ab56 0x7f39938
> > 08 0ee1f594 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> > 09 0ee1f5dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> > 0a 0ee1f644 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> > 0b 0ee1f728 00000000 0x472a179
> >
> > Thread ID: 49
> > System Thread ID: b78
> > Kernel Time: 0:14:43.953
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 00aaf02c 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 00aaf030 77e4905d ntdll!NtReadFile+0xc
> > 02 00aaf098 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 00aaf1cc 0da0223c sx32w!Ordinal19+0x6671
> > 04 00aaf220 0d956862 0xda0223c
> > 05 00aaf26c 0d95672b 0xd956862
> > 06 00aaf2c4 07f39938 0xd95672b
> > 07 00aaf354 7921ab56 0x7f39938
> > 08 00aaf394 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> > 09 00aaf3dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> > 0a 00aaf444 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> > 0b 00aaf528 0e0158d0 0x472a179
> > 0c 0e0158d0 00000000 0xe0158d0
> >
> > Thread ID: 51
> > System Thread ID: bd4
> > Kernel Time: 0:14:40.781
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0f05ef2c 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0f05ef30 77e4905d ntdll!NtReadFile+0xc
> > 02 0f05ef98 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 0f05f0cc 0da0223c sx32w!Ordinal19+0x6671
> > 04 0f05f120 0d956862 0xda0223c
> > 05 0f05f16c 0d95672b 0xd956862
> > 06 0f05f1c4 07f39938 0xd95672b
> > 07 0f05f254 7921ab56 0x7f39938
> > 08 0f05f294 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> > 09 0f05f2dc 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> > 0a 0f05f344 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> > 0b 0f05f428 5900cb38 0x472a179
> > 0c 5900cb38 00000000 0x5900cb38
> >
> >
> >
> >
> > Thread ID: 52
> > System Thread ID: 448
> > Kernel Time: 0:5:1.312
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0f09eeac 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0f09eeb0 77e4905d ntdll!NtReadFile+0xc
> > 02 0f09ef18 0da56671 kernel32!ReadFile+0x16c
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 03 0f09f04c 0da0223c sx32w!Ordinal19+0x6671
> > 04 0f09f0a0 0d956862 0xda0223c
> > 05 0f09f0ec 0d95672b 0xd956862
> > 06 0f09f144 07f39938 0xd95672b
> > 07 0f09f1d4 7921ab56 0x7f39938
> > 08 0f09f214 791b4de8 mscorsvr!ComCallMLStubCache::CompileMLStub+0x1af
> > 09 0f09f25c 7921ab13 mscorsvr!Thread::DoADCallBack+0x5c
> > 0a 0f09f2c4 0472a179 mscorsvr!ComCallMLStubCache::CompileMLStub+0x2ba
> > 0b 0f09f3a8 00000000 0x472a179
> >
> > --
> > Bob
> > Sr. Microsoft Architect
> > Lighthammer Software
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: 2003 Server, quad proc, IIS box - CPU @100% |
|
| Back to top |
|
| |
| Related Topics: | Webgarden\Woker Process\IIS 6.0\Multi-proc server - Correct me if I have this wrong. With webgarden enabled, the IIS worker process will run on one particular cpu and can have multiple worker processes to run on multiple CPUs spreading the load evenly among the CPUs. However, webgarden is disabled by..
The server has encountered an error while loading an appli.. - Hi, I have a very common problem that I have found lots of problem posts similar, but none of the solutions recommended applied to me. My situation is as follows: OS: Windows XP Prof IIS: v5.1 ..NET framework 1.1 and VS.net is installed Error I recieve....
Out-Proc COM+ Problem - Old, very old problem: IIS was running well for several days and suddenly the server stop respond to ANY asp request. HTML or any other requests works fine. Nothing in Event log as well as in IIS Crash tool. Tryed IWAM/IUSR syncronization - no effect. Th...
MSN Through ISA Server 2004 - Hi, I'm trying to give access to a domain user to be able to use MSN only. I've been trying many different configurations, without success..... giving http and https protocol to the whole internet it works fine, though giving MSN Messenger access to...
Win 2K Server/IIS/ASP.Net - I have created a web page that contains a meta-refresh that refreshes the page every 15 minutes. After a few page hits, I need to bounce the world wide web service, because no web browsers can connect to it. When I go in to bounce the service, .. |
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
