Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JVM crash with Java 7 + Agent 1.3.0
See original GitHub issueDescribe the bug We updated apm agent to 1.3.0 yesterday and then after about 18 hours two instances got JVM crash which look pretty similar.
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x000000008fb018d8, pid=122146, tid=140043922573056
Both are using Java 7 (7.0_75 and 7.0_141). One is running on Glassfish 4.0 and the other Payara 4.1.1.171.1.
Debug logs
Current thread (0x00007f7ee0354800): JavaThread "apm-reporter" daemon
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C 0x000000008fb018d8
Also there is co.elastic.apm.agent.report.serialize.DslJsonSerializer::sanitizeTagKey in both compilation events.
Full logs: hs_err_pid122146.log hs_err_pid43918.log
This might be related to elastic/apm-agent-java#444
Issue Analytics
- State:
- Created 5 years ago
- Comments:47 (23 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
About 18h uptime now with 1.3.1-SNAPSHOT without any compile exclusions so seems to work.
1.3.0 with exclusions still ended up crashing after 17h uptime. Last compiled method was
java.lang.invoke.BoundMethodHandle$Species_LL::<init>and nothing else obvious to my eye. Really strange how well it breaks JVM 😃 hs_err_pid27244.log test-20190210_184348.logI think we should use reflection instead of method handles if the agent is running on Java 7.