# ES pure Java? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 2, 2012, 1:11pm UTC](https://discuss.elastic.co/t/es-pure-java/7538 "2012-05-02T13:11:30Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Andrej](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@Andrej](https://discuss.elastic.co/u/Andrej)\ **Post date:** [May 2, 2012, 1:11pm UTC](https://discuss.elastic.co/t/es-pure-java/7538/1 "2012-05-02T13:11:30Z")
Hello, I hope this question does not sound too strange, is elasticsearch pure Java or is it using any connections to native routines? The background is pretty simple, since updating to es 0.19.3 I had several JVM crashes with segmentation faults caused by an elasticsearch thread. So I am trying to figure out if this is a problem of ES or the JVM. I never had problems like this with any other version for over a year now. Does anyone experience the same problem? Thanks! Andrej ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 2, 2012, 4:06pm UTC](https://discuss.elastic.co/t/es-pure-java/7538/2 "2012-05-02T16:06:34Z")
It is in "pure" Java, yea, can you gist your error file? On Wed, May 2, 2012 at 4:11 PM, Andrej Rosenheinrich \< [andrej.rosenheinrich@unister.de](mailto:andrej.rosenheinrich@unister.de)\> wrote: > Hello, > > I hope this question does not sound too strange, is elasticsearch pure > Java or is it using any connections to native routines? The background > is pretty simple, since updating to es 0.19.3 I had several JVM > crashes with segmentation faults caused by an elasticsearch thread. So > I am trying to figure out if this is a problem of ES or the JVM. I > never had problems like this with any other version for over a year > now. > > Does anyone experience the same problem? > > Thanks! > Andrej ---
**Author:** ![Andrej](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@Andrej](https://discuss.elastic.co/u/Andrej)\ **Post date:** [May 3, 2012, 1:01pm UTC](https://discuss.elastic.co/t/es-pure-java/7538/3 "2012-05-03T13:01:59Z")
> > On 2 Mai, 18:06, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > It is in "pure" Java, yea, can you gist your error file? > > On Wed, May 2, 2012 at 4:11 PM, Andrej Rosenheinrich \< > > [andrej.rosenheinr...@unister.de](mailto:andrej.rosenheinr...@unister.de)\> wrote: > > > Hello, > > > I hope this question does not sound too strange, is elasticsearch pure > > Java or is it using any connections to native routines? The background > > is pretty simple, since updating to es 0.19.3 I had several JVM > > crashes with segmentation faults caused by an elasticsearch thread. So > > I am trying to figure out if this is a problem of ES or the JVM. I > > never had problems like this with any other version for over a year > > now. > > > Does anyone experience the same problem? > > > Thanks! > > Andrej ---
**Author:** ![tsuna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsuna/32/2897_2.png) [@tsuna](https://discuss.elastic.co/u/tsuna)\ **Post date:** [May 3, 2012, 4:17pm UTC](https://discuss.elastic.co/t/es-pure-java/7538/4 "2012-05-03T16:17:25Z")
On Thu, May 3, 2012 at 6:01 AM, Andrej Rosenheinrich [andrej.rosenheinrich@unister.de](mailto:andrej.rosenheinrich@unister.de) wrote: > [JVM Error log ES · GitHub](https://gist.github.com/01670f04f86c011980bd) > [JVM Error log ES · GitHub](https://gist.github.com/ca6885a9655399e8958b) I'm not sure what enables you to say the SEGV is "caused by an elasticsearch thread". To me it appears that you're crashing within VMThread, possibly during a GC. I've had weird errors like this in past, and it was often due to failing hardware, most commonly bad memory introducing random SIGSEGV and SIGILL. GC activity tends to tickle failing hardware because it touches a lot of pages in memory. -- Benoit "tsuna" Sigoure Software Engineer @ [www.StumbleUpon.com](http://www.StumbleUpon.com) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 3, 2012, 9:16pm UTC](https://discuss.elastic.co/t/es-pure-java/7538/5 "2012-05-03T21:16:27Z")
Also, try and update the JVM to a new version, you are using 1.6 u24, which has bugs, especially when comrpessed oops are enabled. On Thu, May 3, 2012 at 7:17 PM, tsuna [tsunanet@gmail.com](mailto:tsunanet@gmail.com) wrote: > On Thu, May 3, 2012 at 6:01 AM, Andrej Rosenheinrich > [andrej.rosenheinrich@unister.de](mailto:andrej.rosenheinrich@unister.de) wrote: > > > [JVM Error log ES · GitHub](https://gist.github.com/01670f04f86c011980bd) > > [JVM Error log ES · GitHub](https://gist.github.com/ca6885a9655399e8958b) > > I'm not sure what enables you to say the SEGV is "caused by an > elasticsearch thread". To me it appears that you're crashing within > VMThread, possibly during a GC. > > I've had weird errors like this in past, and it was often due to > failing hardware, most commonly bad memory introducing random SIGSEGV > and SIGILL. GC activity tends to tickle failing hardware because it > touches a lot of pages in memory. > > -- > Benoit "tsuna" Sigoure > Software Engineer @ [www.StumbleUpon.com](http://www.StumbleUpon.com) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:30am UTC](https://discuss.elastic.co/t/es-pure-java/7538/6 "2017-07-06T03:30:10Z")
Closed on July 6, 2017, 3:30am UTC