Re: Using IISState

On Mar 28, 9:27=A0am, Jake wrote:
> On Mar 27, 6:28 pm, "Pat [MSFT]"
> wrote:
>
> > IIS reset itself out from under IISState before all of the threads could=
be
> > logged. =A0No actionable data, though the server did appear to be under =
very
> > little load (free worker threads).
>
> > Pat
>
> > "Jake" wrote in message
>
> >news:519936bd-8593-49b2-9817-193ccf97c22f@x41g2000hsb.googl egroups.com...=

>
> > > Ok, it happened again ... here's the log:
>
> > > Opened log file 'C:\iisstate\output\IISState-5548.log'
>
> > > ***********************
> > > Starting new log output
> > > IISState version 3.3.1
>
> > > Wed Mar 26 13:04:52 2008
>
> > > OS =3D Windows 2003 Server
> > > Executable: w3wp.exe
> > > PID =3D =A05548
>
> > > Note: Thread times are formatted as HH:MM:SS.ms
>
> > > ***********************
>
> > > Thread ID: 0
> > > System Thread ID: 15fc
> > > Kernel Time: 0:0:0.46
> > > User Time: 0:0:0.62
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: HTTP Compression Thread
> > > # ChildEBP RetAddr
> > > 00 0006fc08 7c827d0b ntdll!KiFastSystemCallRet
> > > 01 0006fc0c 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > 02 0006fc7c 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > 03 0006fc90 5a364662 kernel32!WaitForSingleObject+0x12
> > > 04 0006fca0 5a366e3f w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> > > 05 0006fca8 5a3af42d w3dt!UlAtqStartListen+0x2d
> > > 06 0006fcb8 5a3bc335 w3core!W3_SERVER::StartListen+0xbd
> > > 07 0006ff0c 0100187c w3core!UlW3Start+0x26e
> > > 08 0006ff44 01001a27 w3wp!wmain+0x22a
> > > 09 0006ffc0 77e6f23b w3wp!wmainCRTStartup+0x12f
> > > 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
> > > Thread ID: 1
> > > System Thread ID: 720
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Type: Other
> > > # ChildEBP RetAddr
> > > 00 00d0ff9c 7c826f4b ntdll!KiFastSystemCallRet
> > > 01 00d0ffa0 7c83d424 ntdll!NtDelayExecution+0xc
> > > 02 00d0ffb8 77e64829 ntdll!RtlpTimerThread+0x47
> > > 03 00d0ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 2
> > > System Thread ID: 1794
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Type: Other
> > > # ChildEBP RetAddr
> > > 00 00d4ff70 7c8277db ntdll!KiFastSystemCallRet
> > > 01 00d4ff74 7c839f38 ntdll!ZwRemoveIoCompletion+0xc
> > > 02 00d4ffb8 77e64829 ntdll!RtlpWorkerThread+0x3d
> > > 03 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 3
> > > System Thread ID: 17e8
> > > Kernel Time: 0:0:0.15
> > > User Time: 0:0:0.0
> > > Thread Type: Possible ASP page. =A0Possible DCOM activity
> > > Executing Page: Unable to locate ASP page
>
> > > No remote call being made
>
> > > # ChildEBP RetAddr
> > > 00 00dbfe18 7c82783b ntdll!KiFastSystemCallRet
> > > 01 00dbfe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
> > > 02 00dbff84 77c88792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> > > 03 00dbff8c 77c8872d RPCRT4!RecvLotsaCallsWrapper+0xd
> > > 04 00dbffac 77c7b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> > > 05 00dbffb8 77e64829 RPCRT4!ThreadStartRoutine+0x1b
> > > 06 00dbffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 4
> > > System Thread ID: 16f8
> > > Kernel Time: 0:0:0.15
> > > User Time: 0:0:0.0
> > > Thread Type: HTTP Listener
> > > # ChildEBP RetAddr
> > > 00 00fbff24 7c8277db ntdll!KiFastSystemCallRet
> > > 01 00fbff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > 02 00fbff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > 03 00fbff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > 04 00fbffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > 05 00fbffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > 06 00fbffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 5
> > > System Thread ID: 1684
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.62
> > > Thread Type: HTTP Listener
> > > # ChildEBP RetAddr
> > > 00 00ffff24 7c8277db ntdll!KiFastSystemCallRet
> > > 01 00ffff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > 02 00ffff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > 03 00ffff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > 04 00ffffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > 05 00ffffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > 06 00ffffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 6
> > > System Thread ID: 674
> > > Kernel Time: 0:0:0.171
> > > User Time: 0:0:0.140
> > > Thread Type: HTTP Listener
> > > # ChildEBP RetAddr
> > > 00 0104ff24 7c8277db ntdll!KiFastSystemCallRet
> > > 01 0104ff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > 02 0104ff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > 03 0104ff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > 04 0104ffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > 05 0104ffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > 06 0104ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 7
> > > System Thread ID: 1580
> > > Kernel Time: 0:0:0.78
> > > User Time: 0:0:0.109
> > > Thread Type: HTTP Listener
> > > # ChildEBP RetAddr
> > > 00 0108ff24 7c8277db ntdll!KiFastSystemCallRet
> > > 01 0108ff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > 02 0108ff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > 03 0108ff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > 04 0108ffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > 05 0108ffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > 06 0108ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 8
> > > System Thread ID: 11d8
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: Other
> > > # ChildEBP RetAddr
> > > 00 0114fcec 7c827cfb ntdll!KiFastSystemCallRet
> > > 01 0114fcf0 7c83c78e ntdll!NtWaitForMultipleObjects+0xc
> > > 02 0114ffb8 77e64829 ntdll!RtlpWaitThread+0x161
> > > 03 0114ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 9
> > > System Thread ID: 2c8
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: HTTP Compression Thread
> > > # ChildEBP RetAddr
> > > 00 01b1fa84 7c827d0b ntdll!KiFastSystemCallRet
> > > 01 01b1fa88 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > 02 01b1faf8 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > 03 01b1fb0c 5a3b820f kernel32!WaitForSingleObject+0x12
> > > 04 01b1ffb8 77e64829 w3core!HTTP_COMPRESSION::CompressionThread+0x126
> > > 05 01b1ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 10
> > > System Thread ID: 11ac
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Type: Possible ASP page. =A0Possible DCOM activity
> > > Executing Page: Unable to locate ASP page
>
> > > No remote call being made
>
> > > # ChildEBP RetAddr
> > > 00 01b5fe18 7c82783b ntdll!KiFastSystemCallRet
> > > 01 01b5fe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
> > > 02 01b5ff84 77c88792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> > > 03 01b5ff8c 77c8872d RPCRT4!RecvLotsaCallsWrapper+0xd
> > > 04 01b5ffac 77c7b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> > > 05 01b5ffb8 77e64829 RPCRT4!ThreadStartRoutine+0x1b
> > > 06 01b5ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 11
> > > System Thread ID: fb8
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Type: Other
> > > # ChildEBP RetAddr
> > > 00 01b9ff8c 7c826f4b ntdll!KiFastSystemCallRet
> > > 01 01b9ff90 7c81943a ntdll!NtDelayExecution+0xc
> > > 02 01b9ffb8 77e64829 ntdll!RtlpIOWorkerThread+0x3f
> > > 03 01b9ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 12
> > > System Thread ID: a48
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: ASP
> > > Executing Page: Unable to locate ASP page
>
> > > # ChildEBP RetAddr
> > > 00 0279ff0c 7c827d0b ntdll!KiFastSystemCallRet
> > > 01 0279ff10 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > 02 0279ff80 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > 03 0279ff94 709fc803 kernel32!WaitForSingleObject+0x12
> > > 04 0279ffb4 709fc7db asp!CApplnCleanupMgr::ApplnCleanupDoWork+0x1e
> > > 05 0279ffb8 77e64829 asp!CApplnCleanupMgr::ApplnCleanupThread+0xa
> > > 06 0279ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 13
> > > System Thread ID: 14e4
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: ASP
> > > Executing Page: Unable to locate ASP page
>
> > > # ChildEBP RetAddr
> > > 00 02a5fe1c 7c827cfb ntdll!KiFastSystemCallRet
> > > 01 02a5fe20 77e6202c ntdll!NtWaitForMultipleObjects+0xc
> > > 02 02a5fec8 7739bbd1 kernel32!WaitForMultipleObjectsEx+0x11a
> > > 03 02a5ff24 7739ce36 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> > > 04 02a5ff40 709fb8be USER32!MsgWaitForMultipleObjects+0x1f
> > > 05 02a5ff84 77bcb530 asp!CMTACallbackThread::Thread+0x4f
> > > 06 02a5ffb8 77e64829 msvcrt!_endthreadex+0xa3
> > > 07 02a5ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 14
> > > System Thread ID: 1640
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: ASP
> > > Executing Page: Unable to locate ASP page
>
> > > # ChildEBP RetAddr
> > > 00 02a9fe1c 7c827cfb ntdll!KiFastSystemCallRet
> > > 01 02a9fe20 77e6202c ntdll!NtWaitForMultipleObjects+0xc
> > > 02 02a9fec8 7739bbd1 kernel32!WaitForMultipleObjectsEx+0x11a
> > > 03 02a9ff24 7739ce36 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> > > 04 02a9ff40 70a017e9 USER32!MsgWaitForMultipleObjects+0x1f
> > > 05 02a9ff84 77bcb3ca asp!Debugger+0x9e
> > > 06 02a9ffb8 77e64829 msvcrt!_endthread+0xab
> > > 07 02a9ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > Thread ID: 15
> > > System Thread ID: 123c
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > *** ERROR: Symbol file could not be found. =A0Defaulted to export
> > > symbols for C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG
> > > \PDM.DLL -
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: PDM (Debugger) Thread.
> > > # ChildEBP RetAddr
> > > 00 02aefd84 7c827cfb ntdll!KiFastSystemCallRet
> > > 01 02aefd88 77e6202c ntdll!NtWaitForMultipleObjects+0xc
> > > 02 02aefe30 7739bbd1 kernel32!WaitForMultipleObjectsEx+0x11a
> > > 03 02aefe8c 7739ce36 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> > > 04 02aefea8 5166694a USER32!MsgWaitForMultipleObjects+0x1f
> > > WARNING: Stack unwind information not available. Following frames may
> > > be wrong.
> > > 05 02aeff24 77e657fe PDM!DllGetClassObject+0x30a2
> > > 06 02aeff50 02aeff88 kernel32!CreateSemaphoreW+0x5e
> > > 07 02aa2010 00000000 0x2aeff88
>
> > > Thread ID: 16
> > > System Thread ID: 1350
> > > Kernel Time: 0:0:0.0
> > > User Time: 0:0:0.0
> > > Thread Status: Thread is in a WAIT state.
> > > Thread Type: ASP
> > > Executing Page: Unable to locate ASP page
>
> > ...
>
> > read more =BB
>
> Is there any reason why once IIS resets itself, my web service would
> simply be unavailable and uncallable until such time as a reboot?
> Even iisreset does nothing to help reset the service.
>
> We will try to get the dump out quicker next time the service starts
> misbehaving.
>
> Jake


It sounds like your web service crashes the IIS worker process
sufficiently often that IIS simply disabled the Application Pool to
prevent the web service from running (and crashing again). The
Application Pool is re-enabled on reboot. You can also manually
restart the Application Pool again.

Your best bet would be to leave IISState attached to the worker
process waiting for a crash/hang. You have no other choice because
there is no way you can get the dump fast enough.

It is usually ok to do this type of debugging for short periods of
time and for low-volume systems. Real production systems and high-
volume systems require different strategy (i.e. reproduce the issue
elsewhere, not in production).


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//