One of our client is having some weird issue and the cause is yet to be determined.
When the issue happens, many requests get stuck at IIS with RequestAcquireState and stays forever in that state.
This happens very randomly and all the subsequent requests will get stuck.
I have enabled DebugDiag and able to capture dmp file when this happens. But it is very diffcult to analyze and find the root cause of the issue.
I see the error CLR Exception on thread 61 with following error information :
Type: System. Threading.ThreadAbortException
Message: Thread was being aborted.
This exception is originated from webengine4!W3_MGD_HANDLER::ProcessNotification.
Thread 61 - System ID 28036
Entry point clr!Thread::intermediateThreadProc
Create time 2019-05-29 6:15:46 PM
Time spent in user mode 0 Days 00:00:01.390
Time spent in kernel mode 0 Days 00:00:00.078
The thread has evidence of .net exceptions on the stack. Check the Previous .NET Exceptions Report (Exceptions in all .NET Thread Stacks) to view more details of the associated exception
Call Stack
KERNELBASE!RaiseException+68
clr!RaiseTheExceptionInternalOnly+2aa
clr!Thread::HandleThreadAbort+217d0a
clr!UMThunkStubRareDisableWorker+51
clr!UMThunkStub+128
webengine4!W3_MGD_HANDLER::ProcessNotification+8e
webengine4!ProcessNotificationCallback+42
clr!UnManagedPerAppDomainTPCount::DispatchWorkItem+1bc
clr!ThreadpoolMgr::ExecuteWorkRequest+64
clr!ThreadpoolMgr::WorkerThreadStart+f5
clr!Thread::intermediateThreadProc+86
kernel32!BaseThreadInitThunk+14
ntdll!RtlUserThreadStart+21
I have also tried using Win Dbg for this dmp and there is no stack shown even there
Exception object: 0000018210c40650
Exception type: System.Threading.ThreadAbortException
Message: Thread was being aborted.
InnerException: <none>
StackTrace (generated):
<none>
StackTraceString: <none>
HResult: 80131530
Any help will be appreciated.