JVM crash problem on running performance monitoring

Questions about YourKit Java Profiler
Post Reply
vipnaik
Posts: 3
Joined: Wed Dec 13, 2017 11:42 am

JVM crash problem on running performance monitoring

Post by vipnaik »

For monitoring real time performance of JVM we have activated YourKit agent at WebSphere JVM by adding below mentioned JVM generic arguments.
-agentpath:/data/yourkit/YourKit-JavaProfiler-2017.02/bin/linux-x86-64/libyjpagent.so”. After adding this argument and on invoking profiling JVM gets crashed after few minutes.

In native_stderr.log we are getting below error:-
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
Handler1=00007F486FB1C270 Handler2=00007F486F426DB0 InaccessibleAddress=0000000D7F0A3F98
RDI=00000007FEF2EE68 RSI=0000000000000014 RAX=0000000D7F0A3F98 RBX=0000000000000000
RCX=000000000000011D RDX=0000000000000000 R8=0000000000000020 R9=00000007FE824458
R10=0000000000000000 R11=D8632EA33DBF6A25 R12=0000000000000020 R13=0000000580005D70
R14=0000000000000000 R15=0000000580000000
RIP=00007F486D7EFB92 GS=0000 FS=0000 RSP=0000000007644C18
EFlags=0000000000010246 CS=0033 RBP=0000000003EE1C00 ERR=0000000000000004
TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=0000000D7F0A3F98
xmm0 00000007fe824458 (f: 4269949952.000000, d: 1.696361e-313)
xmm1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm2 5c5c5c5c5c5c5c5c (f: 1549556864.000000, d: 8.245487e+136)
xmm3 5c5c5c5c5c5c5c5c (f: 1549556864.000000, d: 8.245487e+136)
xmm4 3d7e03121ec5f7f8 (f: 516290560.000000, d: 1.705984e-12)
xmm5 3fe8687be3b574d6 (f: 3820320000.000000, d: 7.627544e-01)
xmm6 3bbcc86800000000 (f: 0.000000, d: 6.095003e-21)
xmm7 4035c2254f4699e3 (f: 1330027008.000000, d: 2.175838e+01)
xmm8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm9 3c74800000000000 (f: 0.000000, d: 1.778092e-17)
xmm10 3ff0000000000000 (f: 0.000000, d: 1.000000e+00)
xmm11 bec1680000000000 (f: 0.000000, d: -2.074987e-06)
xmm12 3d7dfbbcd7292bf6 (f: 3609799680.000000, d: 1.704356e-12)
xmm13 40357cd0e7026640 (f: 3875694080.000000, d: 2.148756e+01)
xmm14 3c2ce63eab883717 (f: 2877830912.000000, d: 7.833196e-19)
xmm15 40357cd0e7026640 (f: 3875694080.000000, d: 2.148756e+01)
Module=/opt/IBM/WebSphere/AppServer/java_1.8_64/jre/lib/amd64/compressedrefs/libj9jit29.so
Module_base_address=00007F486D593000


Please let me know if anybody else has faced the similar issue.
Vladimir Kondratyev
Posts: 1624
Joined: Tue Aug 10, 2004 7:52 pm

Re: JVM crash problem on running performance monitoring

Post by Vladimir Kondratyev »

What is the exact version of IBM Java you are using? What is output of "java -version"?

Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"
vipnaik
Posts: 3
Joined: Wed Dec 13, 2017 11:42 am

Re: JVM crash problem on running performance monitoring

Post by vipnaik »

Please find the SDK version that we are using can be found below:-
8.0.0.0-WS-WASJavaSDK8-LinuxX64-IFPI89657 : 8.0.0.20171117_1428

CWSDK1004I: Profile base :
CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64
CWSDK1008I: Node iapnode0 SDK name: 1.8_64
CWSDK1009I: Server server1 SDK name: 1.8_64


As per the recommendation by Yourkit support we have applied latest java patch as you can see above.
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: JVM crash problem on running performance monitoring

Post by Anton Katilin »

Please send us to [email protected] the crash log in full (from native_stderr.log; please also check if the JVM creates separate crash log files), and the profiler log file <user home>/.yjp/log/<session name>-<pid>.log
vipnaik
Posts: 3
Joined: Wed Dec 13, 2017 11:42 am

Re: JVM crash problem on running performance monitoring

Post by vipnaik »

We have already contacted support on mail under title "Call Counting Feature of Yourkit is not working"

Kindly check and let us know in case you find any lead.
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: JVM crash problem on running performance monitoring

Post by Anton Katilin »

OK, I see. We have written you our suggestions by email.
latikaahuja
Posts: 1
Joined: Mon Jan 22, 2018 2:23 am

Re: JVM crash problem on running performance monitoring

Post by latikaahuja »

Hi,

What is the resolution of this Segmentation Error.

I am facing the same issue
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: JVM crash problem on running performance monitoring

Post by Anton Katilin »

I see you contacted us by email too. We'll answer your email.
fappel
Posts: 2
Joined: Tue Nov 13, 2018 6:59 am

Re: JVM crash problem on running performance monitoring

Post by fappel »

Hello,

it seems that we are facing a similar problem on an AIX 7.1 with IBM Java 1.8 Version 8.0.3.20 and WebSphere 8.5.5.11 Fixpack Version. The VM crashes while restarting WAS after attaching the agent. The yip log seems to be fine. The excerpt below from the server error log indicates that the segmentation error probably happens in libj9jit28.so:

Unhandled exception
Type=Segmentation error vmState=0x00000000
[...]
Module=/opt/Module_base_address=0900000011F26000
Target=2_80_20161013_322271 (AIX 7.1)
CPU=ppc64 (72 logical CPUs) (0x1c00000000 RAM)WebSphere/AppSystemV855/java_1.8_64/jre/lib/ppc64/compressedrefs/libj9jit28.so

Any help to solve the problem is appreciated.

Kind regards,
Frank Appel
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: JVM crash problem on running performance monitoring

Post by Anton Katilin »

Hi. Could you please try the agent startup option "disablenatives".
fappel
Posts: 2
Joined: Tue Nov 13, 2018 6:59 am

Re: JVM crash problem on running performance monitoring

Post by fappel »

Hi again,

the agent startup option "disablenatives" seems to work.

Thanks
Frank Appel
Post Reply