Hi Shai,
the current Jenkins disables the optimization, with the listed flag. Whenever I update the version, I check if the bug still happens. And it still happens at least with the version currently installed. serv1:/var/lib/jenkins/tools/java/64bit/ibm-j9-jdk7# bin/java -version java version "1.7.0" Java(TM) SE Runtime Environment (build pxa6470_27sr1-20140411_01(SR1)) IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20140410_195893 (JIT enabled, AOT enabled) J9VM - R27_Java727_SR1_20140410_1931_B195893 JIT - tr.r13.java_20140410_61421 GC - R27_Java727_SR1_20140410_1931_B195893_CMPRSS J9CL - 20140410_195893) JCL - 20140409_01 based on Oracle 7u55-b13 I have not yet updated to last J9 version, but the reason for this is the brokenness of the installation (InstallShield in a console, haha). If IBM would provide a simple TAR.GZ file and also a version with the “extended encryption java policy files”, I would do this more often. But currently this costs me half an hour per platform to install this and it is all voluntary! In addition there is no IBM J9 for Java 8, so we don’t run TRUNK tests anymore with J9 (requires Java 8). See my other message about this a while back on this mailing list. Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Shai Erera [mailto:[email protected]] Sent: Wednesday, February 04, 2015 11:02 AM To: [email protected] Subject: FST.pack() J9 bug Hi I was asked by someone in IBM about this bug which is listed under our JavaBugs page: FST.pack() produces corrupt index (Lucene 4) because a loop is miscompiled The J9 team would like to investigate that and they I've asked me for some more details. Since we don't have an issue reported, I searched and came up with several links: http://mail-archives.apache.org/mod_mbox/lucene-dev/201404.mbox/%3Calpine.DEB.2.02.1404031005110.14297@frisbee%3E http://marc.info/?l=solr-dev <http://marc.info/?l=solr-dev&m=134454323703970> &m=134454323703970 Since the Wiki page describes a work around to disable JIT optimization for FST.pack(), I wanted to ask: 1. Are our Jenkins builds with J9 disable this optimization currently? 2. Do we know if this bug still happens? 3. Is there a test which can reproduce the bug (even if it doesn't always reproduce it) so the J9 folks can debug? I am not sure if the tests in the above link are still relevant or were good at reproducing the bug. If it's not easily reproducible, is there additional information besides what's written on the Wiki page that you think can help them investigate this? Shai
