Splunk AppDynamics

JVM Deadlock detected

Sania_Sharma
Explorer

I can see multiple critical violations regarding "Code Deadlock"(JVM Deadlock Detected).

Please explain what does it actually means? Is it affecting any kind of application? How to remove this violation?

Best Regards,

Sania.

Labels (3)
Tags (2)
0 Karma

Nawaz_Ali_Moha1
Contributor

Hello Sania,

In the Events tab do you see any deadlocks? If it does, it indicates that there is a dead lock in the application please have the stack trace checked with the development team and they will be able to fix the issue in the application..

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...