# JVM Crash with APM **URL:** https://discuss.elastic.co/t/jvm-crash-with-apm/250712 **Category:** APM **Tags:** java **Created:** [October 1, 2020, 3:26pm UTC](https://discuss.elastic.co/t/jvm-crash-with-apm/250712 "2020-10-01T15:26:22Z") **Posts on this page:** 1 **Showing post:** 13
### Author: ![Jose\_Angel\_Morena\_Si](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jose_angel_morena_si/32/76522_2.png) [@Jose\_Angel\_Morena\_Si](https://discuss.elastic.co/u/Jose_Angel_Morena_Si) #### Post date: [October 2, 2020, 8:32pm UTC](https://discuss.elastic.co/t/jvm-crash-with-apm/250712/13 "2020-10-02T20:32:27Z")
Hello, I downloaded the 1.17.0 version of the agent from the following link: [https://repo1.maven.org/maven2/co/elastic/apm/apm-agent-attach/1.17.0/apm-agent-attach-1.17.0-standalone.jar and apparently](https://repo1.maven.org/maven2/co/elastic/apm/apm-agent-attach/1.17.0/apm-agent-attach-1.17.0-standalone.jar), the Java process has not died yet, which is great: ```auto [root@company jboss-as-7.1.1]# ps -C java -o pid,etime,cmd PID ELAPSED CMD 28028 09:20:56 /apps/bin/comerzzia/jdk1.7.0_80/bin/java -D[Standalone] -server -Duser.timezone=Europe/Madrid -Xms8192m -Xmx8192m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.cli [root@company jboss-as-7.1.1]# ``` The only problem is that the Transactions in Kibana's APM web page is empty. ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/f/2f97afc50296f37a38d3427cd9fb94444d590bcc.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/b/4bf2c8e3baff624b0d8ff6706729199414d18288.png) These errors were not appearing before. Do I have to downgrade the APM server version? Or is it to do with the apm-server configuration. The apm-server logs are the following: ```auto oct 02 22:27:43 SRVHIDS1 apm-server[23462]: 2020-10-02T22:27:43.882+0200 INFO [publisher_pipeline_output] pipeline/output.go:151 Connection to backoff(elasticsearch(http://192.168.250.114:9200)) established oct 02 22:28:21 SRVHIDS1 apm-server[23462]: 2020-10-02T22:28:21.805+0200 INFO [request] middleware/log_middleware.go:97 request accepted {"request_id": "a07b2586-4a2b-40ca-b311-c24fb983ba3d", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "192.168.250.29", "user-agent": "elasticapm-java/1.17.0", "response_code": 202} oct 02 22:28:51 SRVHIDS1 apm-server[23462]: 2020-10-02T22:28:51.810+0200 INFO [request] middleware/log_middleware.go:97 request accepted {"request_id": "fe94be13-03d0-4ecb-baaf-f8d412425c9f", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "192.168.250.29", "user-agent": "elasticapm-java/1.17.0", "response_code": 202} oct 02 22:29:21 SRVHIDS1 apm-server[23462]: 2020-10-02T22:29:21.804+0200 INFO [request] middleware/log_middleware.go:97 request accepted {"request_id": "a129b39c-dfc4-4da9-ae2b-d38a4e8440a4", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "192.168.250.29", "user-agent": "elasticapm-java/1.17.0", "response_code": 202} oct 02 22:29:51 SRVHIDS1 apm-server[23462]: 2020-10-02T22:29:51.814+0200 INFO [request] middleware/log_middleware.go:97 request accepted {"request_id": "ae94d755-0d1a-44b3-b4dc-a16cd8fed063", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "192.168.250.29", "user-agent": "elasticapm-java/1.17.0", "response_code": 202} ``` My apm-server configuration is the following: ```auto [root@SRVHIDS1 ~]# cat /etc/apm-server/apm-server.yml | grep -v '#' | sed -r '/^\s*$/d' apm-server: host: "192.168.250.114:8200" setup.kibana.host: "192.168.250.114:5601" setup.dashboards.enabled: true logging.level: info logging.to_files: false ssl: enabled: false kibana: enabled: true host: "192.168.250.114:5601" output.elasticsearch: hosts: ["192.168.250.114:9200"] ``` Thank you for all your support, --- _[View the full topic](https://discuss.elastic.co/t/jvm-crash-with-apm/250712)._