AppDynamics has identified a corner case where a 32‐bit .NET application running on a 64‐bit server can experience a crash/hang. This issue is the result of a CLR Profiler API call made by the AppDynamics agent to gather callstack information for snapshots where the callstack has become corrupted. Pending a permanent fix, you can workaround this issue by making the configuration change described below.
This issue affects 32-bit versions of the agent running on a 64-bit server.
Application hang or crash: Instrumentation of a 32-bit application on a 64-bit server can in rare cases result in a crash or hang.
You can work around this issue by changing the method in which AppDynamics collects callstack information for snapshots. This alternative method still provides full visibility into the callstack for slow business transactions, however timings will only be available for exit methods (calls made by the application to SQL/HTTP/WCF/ASMX/MSMQ/etc backends).
Implement the workaround by following the steps below:
In the Controller UI, click App Servers and then any tier to open the tier dashboard.
In the top right corner, click Actions then Configure App Server Agent.
In the left menu of the new window, choose whether to apply the configuration globally or to an individual tier or node.
Select Use Custom Configuration
Click the + sign to add a new agent node property.
Name = disable-sampling
Type = Boolean
- Value = True
- This change will not require a restart of instrumented processes.
This issue is fixed in the .NET Agent version 220.127.116.11 and versions 4.2.3+. Customers who are unable to upgrade the .NET Agent should use the workaround provided.