-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot make HTTPS request with 8u232-b09-jdk-hotspot on armhf #33
Comments
To help track this down: The packages provided by Debian use the cacerts file in |
No luck:
|
Sorry for the delay. It took me a while to dust of my Raspberry Pi. The problem isn't with the cacerts file, but rather with our build. Works flawlessly with Azul Zulu, both 8 and 11.
Somehow, they even managed to get 8 to build with a client VM. Does not work with both AdoptOpenJDK 8 and 11. I tested with our binary builds directly, not with the Debian packages.
@sxa Any idea what we're doing wrong? |
Interesting ... Particularly for 11 there should be no differences between arm32 and all the other platforms. Will aim to take a look during the week ... |
I have the same problem, with the jdk 14, when gradle is downloading the wrapper. |
I built OpenJDK 14.0.1 myself on my Raspberry Pi 4 with a 32 bit Raspbian and the problem is gone.
I ran https://github.com/aahlenst/cacert-test which should produce 1 passing and 1 failing test with the current set of CA certificates bundled with OpenJDK:
So, the problem is clearly with our build setup. OpenSSL bundled with my Raspbian: 1.1.1d-0+deb10u3+rpt1 |
This appears to be fixed in the nightly builds (between 22nd and 23rd of June which was when the gcc compiler for arm32 was updated adoptium/infrastructure#487 (comment) Failing build |
I am able to verify that the problem on arm32 is resolved for the nightly builds of jdk 11 and jdk 14 but still exists with the latest 8u262 nightly. I tested the following binaries:
Whereas the jdk11u and jdk14u arm32 builds show 7.5.0, the jdk8u nightly build configure.txt shows it still configuring and using gcc 5.4.0:
I'm still trying to figure out how everything fits together, but maybe just a dirty workspace for the jdk8u nightly or something else related to the application of adoptium/infrastructure#1406? I didn't see anything else that differed regarding the configuration of the builds. |
Thanks @tmancill - I've got a fix in and we're going to aim to build the new quarterly release this week with the later gcc on JDK8 as well - initial test run is happening at https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-linux-arm-hotspot/324/ - thanks for doing the analysis |
This has been fixed. |
Platform & architecture:
Debian stable (Buster) inside
Docker version 18.06.3-ce, build d7080c1
onLinux arm 4.0.3-armv7-x2 AdoptOpenJDK/openjdk-build#1 SMP Thu May 14 14:30:32 CST 2015 armv7l GNU/Linux
.Having set up adoptopenjdk image with following Dockerfile:
I have created simple example of HTTPS request:
Which compiles fine, but fails with following error:
This exact same
Test.java
file works fine withdefault-jdk (openjdk version "11.0.5" 2019-10-15)
installation from debian repository. What is more interesting above example works just fine on amd64 machine.Cacert file looks fine for me:
Looks like a problem with adoptopenjdk-8-hotspot-armhf build :/
The text was updated successfully, but these errors were encountered: