cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

JVM Crashes & core dumps when Appmon agent is installed within the Application

rinu_dhanaraj
Newcomer

The JVM of my application (Axway API 7.4) is crashing when Appmon JVM args are added to the startup scripts. If removed the application remains healthy.

Axway Version - 7.4.0 SP 5

DynaTrace - 6.5

Java - 64 bit 1.7u80

OS -Linux 64 bit, RHEL 6.7

The core dump generated during the startup has the below details

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Monaco; color: #f4f4f4; background-color: #000000; background-color: rgba(0, 0, 0, 0.85)}
span.s1 {font-variant-ligatures: no-common-ligatures}

A fatal error has been detected by the Java Runtime Environment:

#

# SIGSEGV (0xb) at pc=0x00007f10b14e5579, pid=10251, tid=139706923845376

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Monaco; color: #f4f4f4; background-color: #000000; background-color: rgba(0, 0, 0, 0.85)}
span.s1 {font-variant-ligatures: no-common-ligatures}

JRE version: Java(TM) SE Runtime Environment (7.0_85-b15) (build 1.7.0_85-b15)

# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.85-b06 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# V [libjvm.so+0x640579] jni_SetLongField+0x89

Has any one faced a similar error ? Any inputs would be helpful.

Regards

Rinu

17 REPLIES 17

Joe_Hoffman
Dynatrace Champion
Dynatrace Champion

Rinu, I have seen a few of these types of crashes over the years and they always end up being a bug in the JRE, which is generally already patched and fixed with a newer update of the JRE.

Doing a quick check, I don't see any known bugs in Hotspot that match your pattern. I suggest you open a support case with Dynatrace Support team and they can help you dig into this issue.

If possible,I would try upgrading to the latests version of HotSpot and see if the problem goes away. Also be sure to update to the latest AppMon patch 6.5.10.

rinu_dhanaraj
Newcomer

Thank you Joseph for your quick response.

While I wait to get the support ticket raised, I am trying the JDK upgrade to see if I get through.

I shall keep the forum updated on how this goes.

rinu_dhanaraj
Newcomer

Update : The error remains the same post the JDK upgrade. Going ahead with the support ticket.

harald_berger
Dynatrace Pro
Dynatrace Pro

Hi,

It is a problem in the native code of DWEHttpServletRequest (libHTTP.so)

Stack: [0x00007f100d818000,0x00007f100d919000],  sp=0x00007f100d912350,  free space=1000k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x640579] jni_SetLongField+0x89
C [libHTTP.so+0x60f5f] Vordel::DWEHttpServletRequest_getHeaders(JNIEnv_*, _jobject*, _jstring*)+0xdf
j com.vordel.dwe.http.DWEHttpServletRequest.getHeaders(Ljava/lang/String;)Ljava/util/Enumeration;+0

Please configure the servlet sensor, to not capture ANY http headers and see if the problem persists.

Best

Harry

Hi All,

Actually the only known workaround is to unplace the Servlet sensor or completely exclude the class org.glassfish.jersey.servlet.ServletContainer from transformation, as some headers are captured by default

Best

Harry

mohaideen_shand
Participant

We are also facing exact issue. Can anyone help?

Mohaideen, Did you try removing ANY http header capture as suggested by Harald B?

There are no fixes to this problem to date. As suggested by @Harald B. I removed the servlet sensor which was instrumenting and followed the steps attached in the document.

My case is still open with the vendor trying to see whats causing the crash.

@Rinu D. & @Harald B. When I removed Servlet sensor it works but not getting any useful information in purepath. Are you guys able to get proper purepath in DT.

We placed JVM entry in GroupInstance.

Thanks in advance.

Hi,

You have to define a new custom entry point. Taking a CPU sample might give you an idea which method to instrument. Most likely org.glassfish.jersey.servlet.ServletContainer is a good place.

Best

Harry

raphael_ms
Guide

I am interested in solving the problem, too. Are there any updates?

Thanks in advance, Raphael

harald_berger
Dynatrace Pro
Dynatrace Pro

Hi Raphael,

No, the situation is the same. Axway API is incompatible as it does not fulfill the Servlet spec. So the servlet sensor must be unplaced.

Best

Harry

nima_samsami_ex
Participant

It is also an important Issue for us. Are there any News for Dynatrace 7.0?

Thanks,

Nima

harald_berger
Dynatrace Pro
Dynatrace Pro

Hi Nima,

No, may statement above is till valid.

Best

Harry

chris_geebelen
Dynatrace Mentor
Dynatrace Mentor

I installed Dynatrace on an OAG and defined a custom service based on this method:

com.vordel.dwe.http.HTTPPlugin.ProcessMessage

This gives already some insights but not yet the URL.

Chris

aprasad
Newcomer

I installed Dynatrace on an OAG and defined a custom service based on this method:

com.vordel.dwe.http.HTTPPlugin.ProcessMessage

This gives already some insights but not yet the URL. Do we have a way to see the URL?

gabriel_casella
Dynatrace Pro
Dynatrace Pro

Hi all,

The URL can be seen by instrumenting:

com.vordel.dwe.http.ServerTransaction.getTransactionURI()

and capturing the return value of the method (found that through a CPU sampling).

Tks,