-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b83
-
x86
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8141910 | emb-9 | Roland Westrelin | P3 | Resolved | Fixed | team |
FULL PRODUCT VERSION :
java version "1.9.0-ea"
Java(TM) SE Runtime Environment (build 1.9.0-ea-b78)
Java HotSpot(TM) Server VM (build 1.9.0-ea-b78, mixed mode)
FULL OS VERSION :
Linux serv1 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
EXTRA RELEVANT SYSTEM CONFIGURATION :
CPU: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
(Haswell with AVX2)
A DESCRIPTION OF THE PROBLEM :
During our ongong stress tests (running Apache Lucene) on JDK9 preview builds, we discovered the following bug, which makes it impossible to use Apache Lucene/Solr/Elasticsearch with JDK9:
We are running the Lucene Core Testsuite of the recently released Lucene 5.3.0 Tarball. The tests should pass on any current JVM. Unfortunetely under the following configurations this fails:
- It does not fail with 64 bits (I tried like 20 runs of test suite).
- It does not fail with 32 bits and "-client" (I also tried 20 runs).
- It fails ASAP on 32 bits (in the first few Lucene tests with messages about random NPEs or failed assertions) with: "-server -Xbatch -XX:+TieredCompilation"
- It also fails on 32 bits, but takes longer (like 60 tests of the suite ran): "-server -Xbatch-XX:-TieredCompilation")
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: No
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes
REGRESSION. Last worked in version 8u60
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
thetaphi@serv1:~$ wget http://www.apache.org/dist/lucene/java/5.3.0/lucene-5.3.0-src.tgz
thetaphi@serv1:~$ tar xf lucene-5.3.0-src.tgz
thetaphi@serv1:~$ cd lucene-5.3.0/
thetaphi@serv1:~/lucene-5.3.0$ ant ivy-bootstrap
thetaphi@serv1:~/lucene-5.3.0$ cd core/
thetaphi@serv1:~/lucene-5.3.0/core$ ant test -Dtests.jvms=1 -Dargs='-client'
(passes)
thetaphi@serv1:~/lucene-5.3.0/core$ ant test -Dtests.jvms=1 -Dargs='-server -Xbatch -XX:+TieredCompilation'
(fails after running a few tests)
thetaphi@serv1:~/lucene-5.3.0/core$ ant test -Dtests.jvms=1 -Dargs='-server -Xbatch -XX:-TieredCompilation'
(fails bit later, sometimes whole suite passes)
EXPECTED VERSUS ACTUAL BEHAVIOR :
Lucene Testsuite should pass.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Various test failures:
- NPE
- test assertions fail (e.g. number of returned Lucene search results)
- also Java assertions fail
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
This is impossible for this case, the bug is only triggered on stress testing the whole test suite.
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Use -client compiler or switch to 64 bit JVM.
java version "1.9.0-ea"
Java(TM) SE Runtime Environment (build 1.9.0-ea-b78)
Java HotSpot(TM) Server VM (build 1.9.0-ea-b78, mixed mode)
FULL OS VERSION :
Linux serv1 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
EXTRA RELEVANT SYSTEM CONFIGURATION :
CPU: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
(Haswell with AVX2)
A DESCRIPTION OF THE PROBLEM :
During our ongong stress tests (running Apache Lucene) on JDK9 preview builds, we discovered the following bug, which makes it impossible to use Apache Lucene/Solr/Elasticsearch with JDK9:
We are running the Lucene Core Testsuite of the recently released Lucene 5.3.0 Tarball. The tests should pass on any current JVM. Unfortunetely under the following configurations this fails:
- It does not fail with 64 bits (I tried like 20 runs of test suite).
- It does not fail with 32 bits and "-client" (I also tried 20 runs).
- It fails ASAP on 32 bits (in the first few Lucene tests with messages about random NPEs or failed assertions) with: "-server -Xbatch -XX:+TieredCompilation"
- It also fails on 32 bits, but takes longer (like 60 tests of the suite ran): "-server -Xbatch-XX:-TieredCompilation")
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: No
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes
REGRESSION. Last worked in version 8u60
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
thetaphi@serv1:~$ wget http://www.apache.org/dist/lucene/java/5.3.0/lucene-5.3.0-src.tgz
thetaphi@serv1:~$ tar xf lucene-5.3.0-src.tgz
thetaphi@serv1:~$ cd lucene-5.3.0/
thetaphi@serv1:~/lucene-5.3.0$ ant ivy-bootstrap
thetaphi@serv1:~/lucene-5.3.0$ cd core/
thetaphi@serv1:~/lucene-5.3.0/core$ ant test -Dtests.jvms=1 -Dargs='-client'
(passes)
thetaphi@serv1:~/lucene-5.3.0/core$ ant test -Dtests.jvms=1 -Dargs='-server -Xbatch -XX:+TieredCompilation'
(fails after running a few tests)
thetaphi@serv1:~/lucene-5.3.0/core$ ant test -Dtests.jvms=1 -Dargs='-server -Xbatch -XX:-TieredCompilation'
(fails bit later, sometimes whole suite passes)
EXPECTED VERSUS ACTUAL BEHAVIOR :
Lucene Testsuite should pass.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Various test failures:
- NPE
- test assertions fail (e.g. number of returned Lucene search results)
- also Java assertions fail
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
This is impossible for this case, the bug is only triggered on stress testing the whole test suite.
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Use -client compiler or switch to 64 bit JVM.
- backported by
-
JDK-8141910 Lucene test failures with 32 bit JDK 9b78, Server compiler
-
- Resolved
-
- relates to
-
JDK-8076188 Optimize arraycopy out for non escaping destination
-
- Resolved
-