EM12c: JVM Diagnostics (JVMD) Agent Causes Target JVM to Crash (Doc ID 1540397.1)

Last updated on MARCH 08, 2017

Applies to:

APM - Application Performance Management - Version 12.1.0.3.0 to 12.1.0.3.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms


When trying to run the JVMD agent 12.1.0.3 against a target Java version 1.6.0_29, it is found that the deployed JVMD agent is 
intermittently causing the target JVM of the target server to crash.

An hs_err_pid<PID>.log file will be produced, which will show the JVM crashing on a native JVMD agent library :


Stack: [0x00002b54f5240000,0x00002b54f5c41000],  sp=0x00002b54f5c37d30,  free space=10207k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0x4f0eec]  unsigned+0x4c
C  [libjamagent.so.1+0xd4d16]  JamPushLocalFrame+0x26
C  [libjamagent.so.1+0x9a29e]  JamGetContendedMonitorInfo+0x30
C  [libjamagent.so.1+0x9fc16]  JamShowAllThreadRequest+0x1b8e
C  [libjamagent.so.1+0xa91ff]  JamHandleShowJVMRequest+0xae
C  [libjamagent.so.1+0xe566]  process_data+0x1604
C  [libjamagent.so.1+0x1507a]  unsigned+0x1c21

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms