为应用程序池“应用程序池"提供服务的进程与Windows Process Activation Service发生致命的通信错误 [英] A process serving application pool 'App pool' suffered a fatal communication error with the Windows Process Activation Service

问题描述

我有asp.net Web表单应用程序.我将程序部署到IIS服务器，并且程序运行良好，但是所有用户的InProc会话通常同时死掉. 我知道应用程序池经常是可回收的.我安装了 DebugDiagx64 程序，并在此应用程序池中添加了日志.结果是

I have asp.net web forms application. I deployed program to IIS server and program is working well but all of users' InProc session often die at same time. I know that appliaction pool often is recycle. I instaled DebugDiagx64 program and add log this application pool. Result is that

Some exception details were omitted due to the following reasons
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'NOT_FOUND'
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.Threading.ThreadAbortException'
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.Net.HttpWebRequest'
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.ServiceModel.FaultReason'
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.Threading.ExecutionContext'
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.NullReferenceException'
        The maximum number of total stacks (MAX_CLR_EXCEPTION_STACKS_TOTAL = 100) for all CLR exception types have been collected)
        The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.Security.Cryptography.CryptographicException'

如何解决这个问题?

推荐答案

我发现了问题.我正在使用UDT类型，并且Odac版本有时会引发异常，并且应用程序池被回收.我不使用udt类型，问题已解决.

I found problem. I am using UDT type and Odac version sometimes throw exception and app pool is recycled. I don't use udt type and problem is solved.

这篇关于为应用程序池“应用程序池"提供服务的进程与Windows Process Activation Service发生致命的通信错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！