So I just compiled and executed the simplest HTTP program I could find
import java.io.IOException;
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ReadWebPage {
public static void main(String[] args)
No issue running the openssl command. I’m just on my personal laptop
connecting via my hotspotted phone - I’ve never had any sort of network type
issues like this before. That’s why I wondered whether it was somehow
maven/java related.
Makes no sense to me!
> On 7 Apr 2022, at 11:40 am,
Phil,
Thanks for the additional details, Maven 3.8.1 is recent, so it should work.
The stack trace include the following specific problem:
- java.net.SocketException: Network is unreachable (connect failed)
This indicates a low-level network connectivity problem. Although you
provided the curl
Sure thing David,
phil@Phils-MacBook-Pro nifi % mvn -X -T C2.0 clean install -Pinclude-grpc
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /usr/local/Cellar/maven/3.8.1/libexec
Java version: 11.0.12, vendor: Oracle Corporation,
Phil,
Can you provide the version of Maven you are using? Running Maven with the
-X argument for debug will generate a lot of logging information, but it
might point to the POM resolution problem.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 8:13 PM Phil H wrote:
> I reverted back to AZUL
I reverted back to AZUL JDK 11, and then in turn to Oracle JDK 11, and all had
the same issue.
So I’m assuming it’s either a OSX thing, or some sort of weird maven issue?
> On 7 Apr 2022, at 10:02 am, Mike Thomsen wrote:
>
>> However it’s not a network issue because…
>
> Could be something
Related. You said you're used to building in offline environments. You
were also using a really old build Java 8 early on in the previous
thread. If you're building on a commercial or government network, you
might want to throw the JDK and Maven on a personal laptop and do a
build there.
> However it’s not a network issue because…
Could be something funky with how Java 17's TLS APIs are working on your setup.
Java 8 and Java 11 are your best bets for now anyway. Java 17 support
is still in the early stages and isn't a preferred JDK/JRE.
On Wed, Apr 6, 2022 at 7:00 PM Phil H
So I upgraded to the Azul JDK 17. New repo, following the same instructions as
before.
phil@Phils-MacBook-Pro nifi % mvn -T C2.0 clean install -Pinclude-grpc
[INFO] Scanning for projects...
Downloading from central: