Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
SPECjvm2008_1_01_setup.jar
java-1.6.0-openjdk-javadoc-1.6.0.0-1.39.1.9.8.el6_1.x86_64
java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.x86_64
java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.x86_64
How reproducible:
Steps to Reproduce:
# install SPECjvm2008
java -jar SPECjvm2008_1_01_setup.jar
# run test
cd /SPECjvm2008
java -jar -Xmx1024m SPECjvm2008.jar -ikv
# failed
Actual results:
Error in setup of Benchmark.
spec.harness.StopBenchmarkException: Error invoking bmSetupBenchmarkMethod
at spec.harness.ProgramRunner.invokeBmSetupBenchmark(ProgramRunner.java:185)
at spec.harness.ProgramRunner.runBenchmark(ProgramRunner.java:301)
at spec.harness.ProgramRunner.run(ProgramRunner.java:98)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(libgcj.so.10)
at spec.harness.ProgramRunner.invokeBmSetupBenchmark(ProgramRunner.java:183)
...2 more
Caused by: spec.harness.StopBenchmarkException: Error in setup of crypto.aes.java.security.InvalidParameterException: unsupported key size: 21, valid sizes are: [8, 16, 24]
at spec.benchmarks.crypto.aes.Main.setupBenchmark(Main.java:165)
at java.lang.reflect.Method.invoke(libgcj.so.10)
...3 more
Warmup (120s) begins: Wed Sep 21 12:48:03 LONT 2011
Warmup (120s) ends: Wed Sep 21 12:48:03 LONT 2011
Warmup (120s) result: **NOT VALID**
Errors in benchmark: crypto.aes
Error in setup of Benchmark.
[warmup] Harness interruped during measurement period.
[warmup][bt:1|op:1] spec.harness.StopBenchmarkException: Exception in encrypt for AES/CBC/NoPadding.
Score on crypto.aes: **NOT VALID**
Benchmark crypto.aes failed. Aborting run.
Results are stored in:
/opt/SPECjvm2008/results/SPECjvm2008.001/SPECjvm2008.001.raw
Generating reports in:
/opt/SPECjvm2008/results/SPECjvm2008.001
(.:31554): Gtk-WARNING **: cannot open display:
[root@djt-17-109-v06 SPECjvm2008]# head -25 resYou have new mail in /var/spool/mail/root
Expected results:
Done the benchmark without any error.
Additional info:
java-1.6.0-sun and java-1.6.0-ibm can do it well.
Closing as per comment #3
To clarify further, the run is using GCJ and not OpenJDK. 'alternatives --config java' should be run to set the right JRE first.