Splunk AppDynamics

jvm crash with jdk 8 and AD agent ver 4.3.2.2

CommunityUser
Splunk Employee
Splunk Employee

Hello,

we have noticed  jvm crashes in prod, when we look for stack trace we found AD related classes, no issues on other apps servers where AppDynamic agent is not installed,   can some one help us to figure out the issue?

JAVA: jdk_1_8_0_112

Tomcat: 7.0.56

AD java agent: 4.3.2.2

Stack: [0x00007f01e7f2c000,0x00007f01e802d000],  sp=0x00007f01e802b6e0,  free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
J 1049073 C2 java.util.concurrent.ConcurrentHashMap.get(Ljava/lang/Object;)Ljava/lang/Object; (162 bytes) @ 0x00007f027e1b693c [0x00007f027e1b6900+0x3c]
j  com.singularity.ee.agent.appagent.services.transactionmonitor.instrumentation.b.a()I+150
j  com.singularity.ee.agent.appagent.services.transactionmonitor.instrumentation.b.run()V+7
J 30308 C2 com.singularity.ee.util.javaspecific.scheduler.b.b()V (173 bytes) @ 0x00007f027b728990 [0x00007f027b7287e0+0x1b0]
J 17509 C2 com.singularity.ee.util.javaspecific.scheduler.b.run()V (22 bytes) @ 0x00007f02781c1c40 [0x00007f02781c1c00+0x40]
J 12948 C2 com.singularity.ee.util.javaspecific.scheduler.i.a(Ljava/lang/Runnable;)V (391 bytes) @ 0x00007f02793a4f98 [0x00007f02793a4da0+0x1f8]
J 50022 C2 com.singularity.ee.util.javaspecific.scheduler.i.run()V (67 bytes) @ 0x00007f027ba20d20 [0x00007f027ba20a40+0x2e0]
J 264968 C2 java.lang.Thread.run()V (17 bytes) @ 0x00007f027a1c91ac [0x00007f027a1c9160+0x4c]
v  ~StubRoutines::call_stub
V  [libjvm.so+0x690c66]  JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x1056
V  [libjvm.so+0x691171]  JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x321
V  [libjvm.so+0x691617]  JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*)+0x47
V  [libjvm.so+0x72c990]  thread_entry(JavaThread*, Thread*)+0xa0
V  [libjvm.so+0xa755f3]  JavaThread::thread_main_inner()+0x103
V  [libjvm.so+0xa7573c]  JavaThread::run()+0x11c
V  [libjvm.so+0x926138]  java_start(Thread*)+0x108
C  [libpthread.so.0+0x7dc5]  start_thread+0xc5

thanks

Niranjan

Labels (1)
0 Karma

Brian_Wheeldon
Contributor

Hi Niranjan,

Crashes like this are very rare, so my recommendation is to open a Support ticket at https://help.appdynamics.com/hc/en-us/requests/new

Please provide the stack trace below, and also upload the agent logs and ideally the java core dump file to the case so that the Support team can determine what went wrong.

Regards,

Brian Wheeldon

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...