# JVM crash for Logstash and Elasticsearch 7.1.1

**URL:** https://discuss.elastic.co/t/jvm-crash-for-logstash-and-elasticsearch-7-1-1/186081
**Category:** Elasticsearch
**Tags:** docker
**Created:** [June 17, 2019, 2:01pm UTC](https://discuss.elastic.co/t/jvm-crash-for-logstash-and-elasticsearch-7-1-1/186081 "2019-06-17T14:01:04Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![arberg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arberg/32/93644_2.png) [@arberg](https://discuss.elastic.co/u/arberg)
#### Post date: [June 17, 2019, 2:01pm UTC](https://discuss.elastic.co/t/jvm-crash-for-logstash-and-elasticsearch-7-1-1/186081/1 "2019-06-17T14:01:04Z")

</div>

I'm using the official docker-images for logstash, kibana and elasticsearch, version 7.1.1. I'm getting JVM crashes on elasticsearch and logstash. Sometimes after a few days.

Elasticsearch logs: [https://pastebin.com/h4bkyJPL](https://pastebin.com/h4bkyJPL)  
Logstash dump: [https://pastebin.com/EBV8UEDu](https://pastebin.com/EBV8UEDu)  
Logstash dump2 : [https://pastebin.com/03H8DX9d](https://pastebin.com/03H8DX9d)

This is the header of the dump, indicating OpenJDK 12.0.1+12:

> # 
> 
> # A fatal error has been detected by the Java Runtime Environment:
> 
> # 
> 
> # SIGSEGV (0xb) at pc=0x00007f305cb64401, pid=1, tid=118
> 
> # 
> 
> # JRE version: OpenJDK Runtime Environment (12.0.1+12) (build 12.0.1+12)
> 
> # Java VM: OpenJDK 64-Bit Server VM (12.0.1+12, mixed mode, sharing, tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
> 
> # Problematic frame:
> 
> # J 14287 c2 org.elasticsearch.common.xcontent.support.filtering.FilterPath.compile(Ljava/util/Set;)[Lorg/elasticsearch/common/xcontent/support/filtering/FilterPath; (99 bytes) @ 0x00007f305cb64401 [0x00007f305cb64100+0x0000000000000301]

Any clues?  
Any suggestions for proceeding? Right now I check and start the docker periodically.

---

<div class="post-metadata">

### Author: ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [June 17, 2019, 6:18pm UTC](https://discuss.elastic.co/t/jvm-crash-for-logstash-and-elasticsearch-7-1-1/186081/2 "2019-06-17T18:18:08Z")

</div>

The problematic frame appears to be in Elasticsearch; you would be better off posting in the Elasticsearch forum.

---

<div class="post-metadata">

### Author: ![arberg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arberg/32/93644_2.png) [@arberg](https://discuss.elastic.co/u/arberg)
#### Post date: [June 18, 2019, 2:52pm UTC](https://discuss.elastic.co/t/jvm-crash-for-logstash-and-elasticsearch-7-1-1/186081/3 "2019-06-18T14:52:06Z")

</div>

thx, I've tried moving it to elasticSearch.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 16, 2019, 2:52pm UTC](https://discuss.elastic.co/t/jvm-crash-for-logstash-and-elasticsearch-7-1-1/186081/4 "2019-07-16T14:52:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
