Elastic stack v8.13.3
JVM: -Xms2g -Xmx2g -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=512m -javaagent:/opt/apm/elastic-apm-agent-1.52.1.jar -Delastic.apm.config_file=/opt/apm/elasticapm.properties
elasticapm.properties
agent.log
app run log
I have referenced this discussion: JVM corrupted with java agent 1.19.0 - CentOS - #5 by Eyal_Koren
and deleted the profile_inferred_spans_enabled: true
The application starts normally, the apm is normal
Can anyone tell me why?
Hi, thanks for reporting this!
The discussion you are referring to relates to a very old version that triggered similar JVM crashes, so this is the same symptom and unlikely the same underlying issue.
Inferred spans are a "technical preview" feature as written in the documentation here.
If you really need inferred spans, I would suggest to switch to the EDOT Java agent as it uses a more recent version of async-profiler which is unlikely to trigger the same JVM crash. If it still does, please report it so we can further investigate and maybe help fix this upstream.
1 Like