Bug 1815935
| Summary: | Eclipse (4.15) will not start with java-openjdk 14 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Katzmann <vk2bea> |
| Component: | java-openjdk | Assignee: | Petra Alice Mikova <pmikova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | ahughes, akurtako, jerboaa, jvanek, pmikova |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-18 08:25:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael Katzmann
2020-03-22 21:18:03 UTC
Eclips starts without issue using 'adoptopenjdk' distribution. openjdk version "14" 2020-03-17 OpenJDK Runtime Environment AdoptOpenJDK (build 14+36) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 14+36, mixed mode, sharing) but still fails with the Fedora 31 current distribution in updates-testing: openjdk version "14" 2020-03-17 OpenJDK Runtime Environment 19.9 (build 14+36) OpenJDK 64-Bit Server VM 19.9 (build 14+36, mixed mode, sharing) Commenting jdk.disabled.namedCurves property in /etc/java/java-14-openjdk/java-14-openjdk-14.0.0.36-1.rolling.fc31.x86_64/conf/security/java.security fixes the issue for me. So this is some packaging problem IMHO. Forgot to mention that not only eclipse but maven was failing in similar way prior to commenting the line. java.vendor system property returns "N/A" which is weird at least. Hi, we identified a bug with the curves a while ago, currently testing a candidate fix for the issue. It was caused by a new property in JDK 14 combined with the java-latest-openjdk custom patches, unfortunately it was not causing build failures, only strange behavior. I believe it is the same issue. The packages were already unpushed from testing. Assuming the scratch build passes tests, the new builds should be in testing soon. Thank you! (In reply to Alexander Kurtakov from comment #4) > java.vendor system property returns "N/A" which is weird at least. It could happen that some new --with like: --with-version-build=%{buildver} \ --with-version-pre="%{ea_designator}"\ --with-version-opt=%{lts_designator} \ --with-vendor-version-string="%{vendor_version_string}" \ Which we are passing to spec arrived to openjdk, and there is o default one Afaik it is N/A also in jdk 13 --with-vendor-name Set vendor name. Among others, used to set the
'java.vendor' and 'java.vm.vendor' system
properties. [not specified]
This problem looks to be resolved with java-latest-openjdk-14.0.0.36-3.rolling.fc31.x86_64 |