# IBM JAVA and Elasticsearch

**URL:** <https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090>\
**Category:** Elasticsearch\
**Created:** [July 7, 2015, 9:21pm UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090 "2015-07-07T21:21:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![admurray](https://avatars.discourse-cdn.com/v4/letter/a/ed655f/32.png) [@admurray](https://discuss.elastic.co/u/admurray)\
**Post date:** [July 7, 2015, 9:21pm UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090/1 "2015-07-07T21:21:59Z")

</div>

I am trying to build Elasticsearch on the IBM mainframe, using IBM Java. Does anyone have an estimate on when the 1.7.0 release will be completed? I have had better luck with the master branch than the earlier releases. Also [https://wiki.apache.org/lucene-java/JavaBugs](https://wiki.apache.org/lucene-java/JavaBugs) doesn't list a JIRA issue for the index corruption bug with IBM J9. Is there any update on that? Is the corruption still happening with current versions of J9? Should we open a JIRA issue to track the index corruption bug?

---

<div class="post-metadata">

**Author:** ![ppf2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppf2/32/52219_2.png) [@ppf2](https://discuss.elastic.co/u/ppf2)\
**Post date:** [September 2, 2015, 6:36pm UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090/2 "2015-09-02T18:36:45Z")

</div>

Mike wrote a very nice article on [Lucene and JVM bugs](https://www.elastic.co/blog/lucene-jvm-bugs) and there is a section dedicated to "IBM's J9 JDK joins the fun" which has a link to the list of outstanding issues in the IBM JDK which makes it not ready for prime-time from Lucene's point of view.

---

<div class="post-metadata">

**Author:** ![jpmackl](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@jpmackl](https://discuss.elastic.co/u/jpmackl)\
**Post date:** [January 28, 2016, 8:00pm UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090/3 "2016-01-28T20:00:42Z")

</div>

Hi, Any luck doing this? Are you trying to pull the data from the MF using logstash or another mechanism? We are trying to do the same thing. Thank you!

---

<div class="post-metadata">

**Author:** ![GrahamHannington](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grahamhannington/32/4404_2.png) [@GrahamHannington](https://discuss.elastic.co/u/GrahamHannington)\
**Post date:** [March 22, 2017, 5:16am UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090/4 "2017-03-22T05:16:31Z")

</div>

@jpmackl, you might be interested in my reply to the topic “[Logstash for Mainframes](https://discuss.elastic.co/t/logstash-for-mainframes/58378)”.

---

<div class="post-metadata">

**Author:** ![shanec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shanec/32/4004_2.png) [@shanec](https://discuss.elastic.co/u/shanec)\
**Post date:** [March 22, 2017, 5:19am UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090/5 "2017-03-22T05:19:44Z")

</div>

Please don't bump threads this old.

---

<div class="post-metadata">

**Author:** ![shanec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shanec/32/4004_2.png) [@shanec](https://discuss.elastic.co/u/shanec)\
**Post date:** [March 22, 2017, 5:19am UTC](https://discuss.elastic.co/t/ibm-java-and-elasticsearch/25090/6 "2017-03-22T05:19:52Z")

</div>


