# APM Java Agent:Start up Error **URL:** \ **Category:** APM\ **Created:** [December 13, 2018, 2:24am UTC](https://discuss.elastic.co/t/apm-java-agent-start-up-error/160651 "2018-12-13T02:24:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![azoci](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@azoci](https://discuss.elastic.co/u/azoci)\ **Post date:** [December 13, 2018, 2:24am UTC](https://discuss.elastic.co/t/apm-java-agent-start-up-error/160651/1 "2018-12-13T02:24:58Z")
HI, I'm trying to setup an APM Agent for a java applicaiton ( Spring 5, Webflux ). I got this message when staring an application with apm java agent. bash-4.1# java -javaagent:/home/elastic-apm-agent-1.1.0.jar -Delastic.apm.service\_name=webflux-demo -Delastic.apm.application\_packages=com.azoci.demo.webfluxdemo -Delastic.apm.server\_urls=http://10.178.50.75:8201 -jar webflux-demo-0.0.1-SNAPSHOT.jar 2018-12-13 02:07:19.841 [apm-server-healthcheck] INFO co.elastic.apm.report.ApmServerHealthChecker - Elastic APM server is available: {"ok":{"build\_date":"2018-11-29T22:56:26Z","build\_sha":"ea0bf4863f638b35ecb6ced94f02015bab8bcb47","version":"6.5.2"}} 2018-12-13 02:07:19.911 [main] INFO co.elastic.apm.configuration.StartupInfo - Starting Elastic APM 1.1.0 as webflux-demo on Java 1.8.0\_11 (Oracle Corporation) Linux 3.10.0-693.17.1.el7.x86\_64 . \_\_\_\_ \_ \_\_ \_ \_ /\ / _' \_\_ \_ () \_\_ \_\_ \_ \ \ \ ( ( )\__\_ | '\_ | '_| | '_ / _` | \ \ \ \/ )| |)| | | | | || (| | ) ) ) ) ' | __| .\_\_|| |_|_| |_\__ , | / / / / =========|_|==============|_/=///_/ :: Spring Boot :: (v2.1.1.RELEASE) 2018-12-13 02:07:22.230 INFO 1043 --- [main] c.a.d.w.WebfluxDemoApplication : Starting WebfluxDemoApplication v0.0.1-SNAPSHOT on 242d1917bcb8 with PID 1043 (/home/webflux-demo-0.0.1-SNAPSHOT.jar started by root in /home) 2018-12-13 02:07:22.257 INFO 1043 --- [main] c.a.d.w.WebfluxDemoApplication : No active profile set, falling back to default profiles: default # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fa33f257db1, pid=1043, tid=140339139184384 # # JRE version: Java(TM) SE Runtime Environment (8.0\_11-b12) (build 1.8.0\_11-b12) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.11-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # V [libjvm.so+0x4bddb1] Deoptimization::query\_update\_method\_data(MethodData\*, int, Deoptimization::DeoptReason, unsigned int&, bool&, bool&)+0x31 # # Core dump written. Default location: /home/core or core.1043 # # An error report file with more information is saved as: # /home/hs\_err\_pid1043.log # # If you would like to submit a bug report, please visit: # [http://bugreport.sun.com/bugreport/crash.jsp](http://bugreport.sun.com/bugreport/crash.jsp) # Aborted (core dumped) plz, help me solve this problem. ---
**Author:** ![Eyal\_Koren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_koren/32/36830_2.png) [@Eyal\_Koren](https://discuss.elastic.co/u/Eyal_Koren)\ **Post date:** [December 13, 2018, 6:44am UTC](https://discuss.elastic.co/t/apm-java-agent-start-up-error/160651/2 "2018-12-13T06:44:08Z")
Hi, and thanks for trying out our APM solution. I found [this bug report](https://bugs.openjdk.java.net/browse/JDK-8163574) that seems very similar- looks like your Java version has some problem with some specific ASM instrumentation. If you want to look further into this, here are few things I can suggest trying: 1. Try upgrade the java version (even stay with 8, but take the latest) 2. [Configure the agent to DEBUG logging level](https://www.elastic.co/guide/en/apm/agent/java/current/config-logging.html#config-log-level). Not only it may provide us with more info, but it will enforce some additional bytecode inspection on instrumented classes. 3. Try disabling specific parts of the instrumentation through [this configuration](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-disable-instrumentations) and see if it is only related to a specific part. For example- disable half and see if problem is resolved, then narrow down. If there is a specific instrumentation label that causes that- we will be glad to know. In any case, it says > An error report file with more information is saved as: > /home/hs\_err\_pid1043.log Try to find such error report and attach. Thanks, Eyal ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [December 13, 2018, 8:09am UTC](https://discuss.elastic.co/t/apm-java-agent-start-up-error/160651/3 "2018-12-13T08:09:04Z")
Also note that we don't have auto-instrumentation for Spring WebFlux yet. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 3, 2019, 4:09am UTC](https://discuss.elastic.co/t/apm-java-agent-start-up-error/160651/4 "2019-01-03T04:09:08Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.