AppDomain Shutdown troubleshooting, and investigation
Hi,
At one of your customers we are seeing the following:
dynaTrace:
AppDomain shutdowns and 500 errors
DCRUM:
Session termination errors
These seem to coincide, but I am not able to investigate this further, or I cannot find causes for the AppDomain to shutdown.
Suggestions for how to troubleshoot investigate this further would be much appreciated.
If there are more metrics / instrumentation I can turn on I will.
Hi
Typically an AppDomain is shutdown if
a) there is a severe problem in the .NET Runtime, e.g: Running out of Resources (Memory, Threads, ...) -> here I would look at the process metrics that tell you whether your ASP.NET Engine is running out of memory
b) IIS is scheduled to recycle AppPools on different conditions. In IIS for every AppPool you can configure recycle options such as "every day", "after X requests", "when memory exceeds a certain limit", ... -> so - have a look at your AppPool Settigns in IIS and check the recycle schedule settings
Andi
Hi,
I see Suspension Time and Suspension Count are both Metrics that measures GC (per the description)
But in the "Run Time Suspensions" OOTB dash shows AppDomain Shutdown.
I am not able to find how to make a counter / time measure for the AppDomain Shutdown, so if you could help me with that it would be appreciated.
Also this is not an App Pool recycle, it is a AppDomain Shutdown.
Any suggestions?
Hi. Sorry for the late reply. There is no measure in the moment that tells you how often a pool recycled or was shutdown.
The Suspension Time in the Runtime Suspension Dashlet can be charted. The measure you need to look into is called "PurePath Suspension Duration" or "MEthods -> Exec Suspension Time".
