# Java fatal error with elasticsearch and kibana

**URL:** https://discuss.elastic.co/t/java-fatal-error-with-elasticsearch-and-kibana/48721
**Category:** Elasticsearch
**Created:** [April 28, 2016, 6:01pm UTC](https://discuss.elastic.co/t/java-fatal-error-with-elasticsearch-and-kibana/48721 "2016-04-28T18:01:59Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [May 2, 2016, 7:07am UTC](https://discuss.elastic.co/t/java-fatal-error-with-elasticsearch-and-kibana/48721/2 "2016-05-02T07:07:20Z")

</div>

Hi,

this already came up earlier: [openJDK on ARM crashes Elastic](https://discuss.elastic.co/t/openjdk-on-arm-crashes-elastic/27283)

The problem is that your JVM implementation does not know what to do with a specific bytecode instruction (opcode 232). The funny thing is that the [JVM specification](http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-6.html#jvms-6.5) does not define such an opcode so I guess bytecode parsing already tripped earlier (although this is really just a wild guess). You should either ask in an Icedtea forum or file a bug at the Icedtea bugzilla.

Daniel

---

_[View the full topic](https://discuss.elastic.co/t/java-fatal-error-with-elasticsearch-and-kibana/48721)._