Re: Possible protocol error, handshake_error when using Maven
The checksum incorrect can be caused by hardware features or truncated packets, it is normally not a sign you have to care about. You can specify -K to ignore it. Try tcpdump -nnpvKX to get the packet content. But I would write the capture to a file and use Wireshark to visualize the tls handshake (or TLS-hello-dump or ssldump). But the java debug trace should be much easier to read it will show the TLS flags in text. Gruss Bernd -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet: Monday, February 21, 2022 11:25:46 PM An: Maven Users List Betreff: RE: Possible protocol error, handshake_error when using Maven I did a tcpdump, but felt it was off topic to post it here. But since you brought it up, this is what command I used and the output when I ran the following command: java GetUrls https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom sudo tcpdump -ni eno1 "tcp port 443 and (tcp[((tcp[12] & 0xf0) >> 2)] = 0x16)" -vv [sudo] password for millerc: tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes 14:24:28.325528 IP (tos 0x0, ttl 64, id 2230, offset 0, flags [DF], proto TCP (6), length 297) 10.XX.XXX.XXX.52022 > 146.75.36.215.https: Flags [P.], cksum 0x8708 (incorrect -> 0xb913), seq 1440532052:1440532297, ack 2840419613, win 229, options [nop,nop,TS val 1152993612 ecr 2048890113], length I see incorrect entry. -Original Message- From: Bernd Eckenfels Sent: Monday, February 21, 2022 3:36 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. The exception means that the other side closed the connection with an alert message. So it is a bit hard to say why it did that (without looking in the server logfile). However the normal reasons for that is only missing agreement on protocol or cipher (not certificates). There can now be 2 problems, one is that you are not connecting to the correct server but maybe a firewall or proxy appliance. The other option is that your client (your JSSE client in Java runtime) is not supporting the usual ciphers and protocols. There could be a number of reasons (maybe FIPS hardening or modified jcl or net.properties or security.properties). I would turn on the verbose JSSE debug messages or do a tcpdump. Both should show you what the client is suggesting for protocol and ciphers in the ClientHello message. (If those look fine you need to look at the other side). Try java -Djavax.net.debug=all GetUrl Gruss Bernd -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet: Monday, February 21, 2022 8:32:59 PM An: Maven Users List Betreff: RE: Possible protocol error, handshake_error when using Maven Sorry for the late reply, I'm still troubleshooting this and went back and re-read what was written and now understand it. I'm still getting handshake_failure when running the following command: [cmiller@gungan java]$ java GetUrls https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom Exception in thread "main" javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at sun.security.ssl.Alert.createSSLException(Alert.java:131) at sun.security.ssl.Alert.createSSLException(Alert.java:117) at sun.security.ssl.TransportContext.fatal(TransportContext.java:311) at sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:293) at sun.security.ssl.TransportContext.dispatch(TransportContext.java:185) at sun.security.ssl.SSLTransport.decode(SSLTransport.java:152) at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1392) at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1300) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:435) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:197) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) at GetUrls.main(GetUrls.java:10) For the sake of troubleshooting, I've also done the following. Upgraded the Red Hat package ca-certificates to 2021.2.50 and still have the same issue. For Java,
RE: Possible protocol error, handshake_error when using Maven
I did a tcpdump, but felt it was off topic to post it here. But since you brought it up, this is what command I used and the output when I ran the following command: java GetUrls https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom sudo tcpdump -ni eno1 "tcp port 443 and (tcp[((tcp[12] & 0xf0) >> 2)] = 0x16)" -vv [sudo] password for millerc: tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes 14:24:28.325528 IP (tos 0x0, ttl 64, id 2230, offset 0, flags [DF], proto TCP (6), length 297) 10.XX.XXX.XXX.52022 > 146.75.36.215.https: Flags [P.], cksum 0x8708 (incorrect -> 0xb913), seq 1440532052:1440532297, ack 2840419613, win 229, options [nop,nop,TS val 1152993612 ecr 2048890113], length I see incorrect entry. -Original Message- From: Bernd Eckenfels Sent: Monday, February 21, 2022 3:36 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. The exception means that the other side closed the connection with an alert message. So it is a bit hard to say why it did that (without looking in the server logfile). However the normal reasons for that is only missing agreement on protocol or cipher (not certificates). There can now be 2 problems, one is that you are not connecting to the correct server but maybe a firewall or proxy appliance. The other option is that your client (your JSSE client in Java runtime) is not supporting the usual ciphers and protocols. There could be a number of reasons (maybe FIPS hardening or modified jcl or net.properties or security.properties). I would turn on the verbose JSSE debug messages or do a tcpdump. Both should show you what the client is suggesting for protocol and ciphers in the ClientHello message. (If those look fine you need to look at the other side). Try java -Djavax.net.debug=all GetUrl Gruss Bernd -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet: Monday, February 21, 2022 8:32:59 PM An: Maven Users List Betreff: RE: Possible protocol error, handshake_error when using Maven Sorry for the late reply, I'm still troubleshooting this and went back and re-read what was written and now understand it. I'm still getting handshake_failure when running the following command: [cmiller@gungan java]$ java GetUrls https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom Exception in thread "main" javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at sun.security.ssl.Alert.createSSLException(Alert.java:131) at sun.security.ssl.Alert.createSSLException(Alert.java:117) at sun.security.ssl.TransportContext.fatal(TransportContext.java:311) at sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:293) at sun.security.ssl.TransportContext.dispatch(TransportContext.java:185) at sun.security.ssl.SSLTransport.decode(SSLTransport.java:152) at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1392) at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1300) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:435) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:197) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) at GetUrls.main(GetUrls.java:10) For the sake of troubleshooting, I've also done the following. Upgraded the Red Hat package ca-certificates to 2021.2.50 and still have the same issue. For Java, there is a UI Control Panel, where I unchecked both TLS 1.0 and 1.1 and still having the same issue. Thanks again to everyone for helping with this. -Original Message- From: Bernd Eckenfels Sent: Friday, February 4, 2022 2:02 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. Yes that's expected. What does the next command print. -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet:
Re: Possible protocol error, handshake_error when using Maven
The exception means that the other side closed the connection with an alert message. So it is a bit hard to say why it did that (without looking in the server logfile). However the normal reasons for that is only missing agreement on protocol or cipher (not certificates). There can now be 2 problems, one is that you are not connecting to the correct server but maybe a firewall or proxy appliance. The other option is that your client (your JSSE client in Java runtime) is not supporting the usual ciphers and protocols. There could be a number of reasons (maybe FIPS hardening or modified jcl or net.properties or security.properties). I would turn on the verbose JSSE debug messages or do a tcpdump. Both should show you what the client is suggesting for protocol and ciphers in the ClientHello message. (If those look fine you need to look at the other side). Try java -Djavax.net.debug=all GetUrl Gruss Bernd -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet: Monday, February 21, 2022 8:32:59 PM An: Maven Users List Betreff: RE: Possible protocol error, handshake_error when using Maven Sorry for the late reply, I'm still troubleshooting this and went back and re-read what was written and now understand it. I'm still getting handshake_failure when running the following command: [cmiller@gungan java]$ java GetUrls https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom Exception in thread "main" javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at sun.security.ssl.Alert.createSSLException(Alert.java:131) at sun.security.ssl.Alert.createSSLException(Alert.java:117) at sun.security.ssl.TransportContext.fatal(TransportContext.java:311) at sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:293) at sun.security.ssl.TransportContext.dispatch(TransportContext.java:185) at sun.security.ssl.SSLTransport.decode(SSLTransport.java:152) at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1392) at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1300) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:435) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:197) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) at GetUrls.main(GetUrls.java:10) For the sake of troubleshooting, I've also done the following. Upgraded the Red Hat package ca-certificates to 2021.2.50 and still have the same issue. For Java, there is a UI Control Panel, where I unchecked both TLS 1.0 and 1.1 and still having the same issue. Thanks again to everyone for helping with this. -Original Message- From: Bernd Eckenfels Sent: Friday, February 4, 2022 2:02 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. Yes that's expected. What does the next command print. -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet: Friday, February 4, 2022 7:39:44 PM An: Maven Users List Betreff: RE: Possible protocol error, handshake_error when using Maven No output when running the following command: javac GetURLS.java Just getting GetUrls.class file. Thanks -Original Message- From: Bernd Eckenfels Sent: Friday, February 4, 2022 12:54 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. The javac command creates the .class file the java command executes it (modern java also can execute the .Java file). What is the output of the last java command in your case? (You also might ask internally a developer) -- http://bernd.eckenfels.net Von: christopher.mil...@gd-ms.com Gesendet: Friday, February 4, 2022 6:32:49 PM An: Maven Users List Betreff: RE: Possible protocol error, handshake_error when using Maven Sorry for the late reply, busy week. I ran this on my RHEL 8 workstation, and didn't get any output, other then a new file was creat
RE: Possible protocol error, handshake_error when using Maven
Sorry for the late reply, I'm still troubleshooting this and went back and
re-read what was written and now understand it.
I'm still getting handshake_failure when running the following command:
[cmiller@gungan java]$ java GetUrls
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
Exception in thread "main" javax.net.ssl.SSLHandshakeException: Received fatal
alert: handshake_failure
at sun.security.ssl.Alert.createSSLException(Alert.java:131)
at sun.security.ssl.Alert.createSSLException(Alert.java:117)
at sun.security.ssl.TransportContext.fatal(TransportContext.java:311)
at sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:293)
at sun.security.ssl.TransportContext.dispatch(TransportContext.java:185)
at sun.security.ssl.SSLTransport.decode(SSLTransport.java:152)
at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1392)
at
sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1300)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:435)
at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:197)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352)
at GetUrls.main(GetUrls.java:10)
For the sake of troubleshooting, I've also done the following. Upgraded the
Red Hat package ca-certificates to 2021.2.50 and still have the same issue.
For Java, there is a UI Control Panel, where I unchecked both TLS 1.0 and 1.1
and still having the same issue.
Thanks again to everyone for helping with this.
-Original Message-
From: Bernd Eckenfels
Sent: Friday, February 4, 2022 2:02 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
Yes that's expected. What does the next command print.
--
http://bernd.eckenfels.net
Von: christopher.mil...@gd-ms.com
Gesendet: Friday, February 4, 2022 7:39:44 PM
An: Maven Users List
Betreff: RE: Possible protocol error, handshake_error when using Maven
No output when running the following command: javac GetURLS.java
Just getting GetUrls.class file.
Thanks
-Original Message-
From: Bernd Eckenfels
Sent: Friday, February 4, 2022 12:54 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
The javac command creates the .class file the java command executes it (modern
java also can execute the .Java file). What is the output of the last java
command in your case? (You also might ask internally a developer)
--
http://bernd.eckenfels.net
Von: christopher.mil...@gd-ms.com
Gesendet: Friday, February 4, 2022 6:32:49 PM
An: Maven Users List
Betreff: RE: Possible protocol error, handshake_error when using Maven
Sorry for the late reply, busy week.
I ran this on my RHEL 8 workstation, and didn't get any output, other then a
new file was created, called GetUrls.class. Didn't get the output you have
below. Disclosure, I'm not a software developer by trade, so bear with me.
Thanks
-Original Message-
From: Nils Breunese
Sent: Tuesday, February 1, 2022 12:13 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
christopher.mil...@gd-ms.com wrote:
> I was able to curl that URL along with pulling that .pom file with the
> following command:
>
> curl -o maven-archiver-2.5.pom
> https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
>
> So I'm still at a loss where I'm experiencing this issue currently.
Have you tried fetching that URL from a simple Java program to check whether
your Java stack can access that URL?
--
? cat GetUrls.java
import java.net.HttpURLConnection;
import java.net.URL;
class GetUrls {
public static void main(String[] args) throws Exception {
for (Strin
Re: Possible protocol error, handshake_error when using Maven
Yes that’s expected. What does the next command print.
--
http://bernd.eckenfels.net
Von: christopher.mil...@gd-ms.com
Gesendet: Friday, February 4, 2022 7:39:44 PM
An: Maven Users List
Betreff: RE: Possible protocol error, handshake_error when using Maven
No output when running the following command: javac GetURLS.java
Just getting GetUrls.class file.
Thanks
-Original Message-
From: Bernd Eckenfels
Sent: Friday, February 4, 2022 12:54 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
The javac command creates the .class file the java command executes it (modern
java also can execute the .Java file). What is the output of the last java
command in your case? (You also might ask internally a developer)
--
http://bernd.eckenfels.net
Von: christopher.mil...@gd-ms.com
Gesendet: Friday, February 4, 2022 6:32:49 PM
An: Maven Users List
Betreff: RE: Possible protocol error, handshake_error when using Maven
Sorry for the late reply, busy week.
I ran this on my RHEL 8 workstation, and didn't get any output, other then a
new file was created, called GetUrls.class. Didn't get the output you have
below. Disclosure, I'm not a software developer by trade, so bear with me.
Thanks
-Original Message-
From: Nils Breunese
Sent: Tuesday, February 1, 2022 12:13 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
christopher.mil...@gd-ms.com wrote:
> I was able to curl that URL along with pulling that .pom file with the
> following command:
>
> curl -o maven-archiver-2.5.pom
> https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
>
> So I'm still at a loss where I'm experiencing this issue currently.
Have you tried fetching that URL from a simple Java program to check whether
your Java stack can access that URL?
--
? cat GetUrls.java
import java.net.HttpURLConnection;
import java.net.URL;
class GetUrls {
public static void main(String[] args) throws Exception {
for (String arg : args) {
URL url = new URL(arg);
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("GET");
int status = con.getResponseCode();
System.out.println("[" + status + "] " + url);
}
}
}
? javac GetUrls.java
? java GetUrls
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
[200]
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
--
Nils.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Possible protocol error, handshake_error when using Maven
No output when running the following command: javac GetURLS.java
Just getting GetUrls.class file.
Thanks
-Original Message-
From: Bernd Eckenfels
Sent: Friday, February 4, 2022 12:54 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
The javac command creates the .class file the java command executes it (modern
java also can execute the .Java file). What is the output of the last java
command in your case? (You also might ask internally a developer)
--
http://bernd.eckenfels.net
Von: christopher.mil...@gd-ms.com
Gesendet: Friday, February 4, 2022 6:32:49 PM
An: Maven Users List
Betreff: RE: Possible protocol error, handshake_error when using Maven
Sorry for the late reply, busy week.
I ran this on my RHEL 8 workstation, and didn't get any output, other then a
new file was created, called GetUrls.class. Didn't get the output you have
below. Disclosure, I'm not a software developer by trade, so bear with me.
Thanks
-Original Message-
From: Nils Breunese
Sent: Tuesday, February 1, 2022 12:13 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
christopher.mil...@gd-ms.com wrote:
> I was able to curl that URL along with pulling that .pom file with the
> following command:
>
> curl -o maven-archiver-2.5.pom
> https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
>
> So I'm still at a loss where I'm experiencing this issue currently.
Have you tried fetching that URL from a simple Java program to check whether
your Java stack can access that URL?
--
? cat GetUrls.java
import java.net.HttpURLConnection;
import java.net.URL;
class GetUrls {
public static void main(String[] args) throws Exception {
for (String arg : args) {
URL url = new URL(arg);
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("GET");
int status = con.getResponseCode();
System.out.println("[" + status + "] " + url);
}
}
}
? javac GetUrls.java
? java GetUrls
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
[200]
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
--
Nils.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible protocol error, handshake_error when using Maven
The javac command creates the .class file the java command executes it (modern
java also can execute the .Java file). What is the output of the last java
command in your case? (You also might ask internally a developer)
--
http://bernd.eckenfels.net
Von: christopher.mil...@gd-ms.com
Gesendet: Friday, February 4, 2022 6:32:49 PM
An: Maven Users List
Betreff: RE: Possible protocol error, handshake_error when using Maven
Sorry for the late reply, busy week.
I ran this on my RHEL 8 workstation, and didn't get any output, other then a
new file was created, called GetUrls.class. Didn't get the output you have
below. Disclosure, I'm not a software developer by trade, so bear with me.
Thanks
-Original Message-
From: Nils Breunese
Sent: Tuesday, February 1, 2022 12:13 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
christopher.mil...@gd-ms.com wrote:
> I was able to curl that URL along with pulling that .pom file with the
> following command:
>
> curl -o maven-archiver-2.5.pom
> https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
>
> So I'm still at a loss where I'm experiencing this issue currently.
Have you tried fetching that URL from a simple Java program to check whether
your Java stack can access that URL?
--
? cat GetUrls.java
import java.net.HttpURLConnection;
import java.net.URL;
class GetUrls {
public static void main(String[] args) throws Exception {
for (String arg : args) {
URL url = new URL(arg);
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("GET");
int status = con.getResponseCode();
System.out.println("[" + status + "] " + url);
}
}
}
? javac GetUrls.java
? java GetUrls
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
[200]
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
--
Nils.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Possible protocol error, handshake_error when using Maven
Sorry for the late reply, busy week.
I ran this on my RHEL 8 workstation, and didn't get any output, other then a
new file was created, called GetUrls.class. Didn't get the output you have
below. Disclosure, I'm not a software developer by trade, so bear with me.
Thanks
-Original Message-
From: Nils Breunese
Sent: Tuesday, February 1, 2022 12:13 PM
To: Maven Users List
Subject: Re: Possible protocol error, handshake_error when using Maven
External E-mail --- CAUTION: This email originated from outside GDMS. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
christopher.mil...@gd-ms.com wrote:
> I was able to curl that URL along with pulling that .pom file with the
> following command:
>
> curl -o maven-archiver-2.5.pom
> https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
>
> So I'm still at a loss where I'm experiencing this issue currently.
Have you tried fetching that URL from a simple Java program to check whether
your Java stack can access that URL?
--
? cat GetUrls.java
import java.net.HttpURLConnection;
import java.net.URL;
class GetUrls {
public static void main(String[] args) throws Exception {
for (String arg : args) {
URL url = new URL(arg);
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("GET");
int status = con.getResponseCode();
System.out.println("[" + status + "] " + url);
}
}
}
? javac GetUrls.java
? java GetUrls
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
[200]
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
--
Nils.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible protocol error, handshake_error when using Maven
christopher.mil...@gd-ms.com wrote:
> I was able to curl that URL along with pulling that .pom file with the
> following command:
>
> curl -o maven-archiver-2.5.pom
> https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
>
> So I'm still at a loss where I'm experiencing this issue currently.
Have you tried fetching that URL from a simple Java program to check whether
your Java stack can access that URL?
——
❯ cat GetUrls.java
import java.net.HttpURLConnection;
import java.net.URL;
class GetUrls {
public static void main(String[] args) throws Exception {
for (String arg : args) {
URL url = new URL(arg);
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("GET");
int status = con.getResponseCode();
System.out.println("[" + status + "] " + url);
}
}
}
❯ javac GetUrls.java
❯ java GetUrls
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
[200]
https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom
——
Nils.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Possible protocol error, handshake_error when using Maven
No were not using our Nexus repo as a proxy for Maven central. Not my decision, and I don't have a voice in how its use. I was able to curl that URL along with pulling that .pom file with the following command: curl -o maven-archiver-2.5.pom https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom So I'm still at a loss where I'm experiencing this issue currently. I have local IT support that is aware of the issue, if we make any progress I'll let everyone know. Thanks -Original Message- From: Nils Breunese Sent: Monday, January 31, 2022 5:35 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. christopher.mil...@gd-ms.com wrote: > Yes, we have a local Nexus repo where I can use curl command to > upload/download without errors. When you have issues it's when Maven is trying to download something directly from repo.maven.apache.org? So you don't use your Nexus instance as a proxy for Maven Central, right? Your Nexus will use a different TLS certificate chain than repo.maven.apache.org, so not having the correct CA certificate for Maven Central could still be the issue. Does this command work on your machine? curl https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom If so, does getting that URL from a simple Java program work on your machine? Nils. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible protocol error, handshake_error when using Maven
christopher.mil...@gd-ms.com wrote: > Yes, we have a local Nexus repo where I can use curl command to > upload/download without errors. When you have issues it’s when Maven is trying to download something directly from repo.maven.apache.org? So you don’t use your Nexus instance as a proxy for Maven Central, right? Your Nexus will use a different TLS certificate chain than repo.maven.apache.org, so not having the correct CA certificate for Maven Central could still be the issue. Does this command work on your machine? curl https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom If so, does getting that URL from a simple Java program work on your machine? Nils. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Possible protocol error, handshake_error when using Maven
Yes, we have a local Nexus repo where I can use curl command to upload/download without errors. -Original Message- From: Nils Breunese Sent: Friday, January 28, 2022 3:23 PM To: Maven Users List Subject: Re: Possible protocol error, handshake_error when using Maven Can you the POM file directly without Maven or Java? curl https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom Isn't RHEL 8.1 also in need of an update? I believe RHEL 8.4 is current? Nils. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible protocol error, handshake_error when using Maven
I’m not sure, but I suspect RHEL 8.1 might have some outdated CA certificates. I think that updating to the latest RHEL update (8.4?) might resolve this issue. Nils. > Op 31 jan. 2022, om 16:01 heeft christopher.mil...@gd-ms.com het volgende > geschreven: > > > Here is the java output: > > $ java -version > openjdk version "1.8.0_302" > OpenJDK Runtime Environment (build 1.8.0_302-b08) > OpenJDK 64-Bit Server VM (build 25.302-b08, mixed mode) > > $ echo JAVA_HOME > /etc/alternatives/java_sdk_1.8.0_openjdk > > > I'm chatting with a few co-workers and they might be having issues with Maven > as well. Have to dig into here more here. > > Thanks > > > > > -Original Message- > From: Karl Heinz Marbaise > Sent: Saturday, January 29, 2022 5:08 AM > To: Maven Users List ; Miller, Christopher (NE) > > Subject: Re: Possible protocol error, handshake_error when using Maven > > > External E-mail --- CAUTION: This email originated from outside GDMS. Do not > click links or open attachments unless you recognize the sender and know the > content is safe. > > Hi, > > > can you please write which exact version of the JDK you are using? > Furthermore the Maven version you are using a bit out of time... > Simplest try would be to upgrade to most recent version of Maven... > > > Kind regards > Karl Heinz Marbaise > On 28.01.22 18:08, christopher.mil...@gd-ms.com wrote: >> >> >> Using Maven 3.5.4 on RHEL 8.1 with OpenJDK 1.8. >> >> I've been using maven okay for awhile now and now I'm getting the following >> error when running a pom.xml file. >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-jar-plugin:2.4:jar (default-jar) on project >> SOFTWARE_Build_Media: Execution default-jar of goal >> org.apache.maven.plugins:maven-jar-plugin:2.4:jar failed: Plugin >> org.apache.maven.plugins:maven-jar-plugin:2.4 or one of its dependencies >> could not be resolved: Failed to collect dependencies at >> org.apache.maven.plugins:maven-jar-plugin:jar:2.4 -> >> org.apache.maven:maven-archiver:jar:2.5: Failed to read artifact descriptor >> for org.apache.maven:maven-archiver:jar:2.5: Could not transfer artifact >> org.apache.maven:maven-archiver:pom:2.5 from/to central >> (https://repo.maven.apache.org/maven2): Received fatal alert: >> handshake_failure -> [Help 1] >> >> >> If I add -X to the end of my mvn command, I see this error often: >> >> Received fatal alert: handshake_failure >> >> >> Googling around, might be a TLS mismatch issue. Is there anyway to tell and >> correct it? >> >> >> I've tried to add the following tag to my settings.xml, >> true and get the same error. >> >> Thanks >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Possible protocol error, handshake_error when using Maven
Here is the java output: $ java -version openjdk version "1.8.0_302" OpenJDK Runtime Environment (build 1.8.0_302-b08) OpenJDK 64-Bit Server VM (build 25.302-b08, mixed mode) $ echo JAVA_HOME /etc/alternatives/java_sdk_1.8.0_openjdk I'm chatting with a few co-workers and they might be having issues with Maven as well. Have to dig into here more here. Thanks -Original Message- From: Karl Heinz Marbaise Sent: Saturday, January 29, 2022 5:08 AM To: Maven Users List ; Miller, Christopher (NE) Subject: Re: Possible protocol error, handshake_error when using Maven External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, can you please write which exact version of the JDK you are using? Furthermore the Maven version you are using a bit out of time... Simplest try would be to upgrade to most recent version of Maven... Kind regards Karl Heinz Marbaise On 28.01.22 18:08, christopher.mil...@gd-ms.com wrote: > > > Using Maven 3.5.4 on RHEL 8.1 with OpenJDK 1.8. > > I've been using maven okay for awhile now and now I'm getting the following > error when running a pom.xml file. > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-jar-plugin:2.4:jar (default-jar) on project > SOFTWARE_Build_Media: Execution default-jar of goal > org.apache.maven.plugins:maven-jar-plugin:2.4:jar failed: Plugin > org.apache.maven.plugins:maven-jar-plugin:2.4 or one of its dependencies > could not be resolved: Failed to collect dependencies at > org.apache.maven.plugins:maven-jar-plugin:jar:2.4 -> > org.apache.maven:maven-archiver:jar:2.5: Failed to read artifact descriptor > for org.apache.maven:maven-archiver:jar:2.5: Could not transfer artifact > org.apache.maven:maven-archiver:pom:2.5 from/to central > (https://repo.maven.apache.org/maven2): Received fatal alert: > handshake_failure -> [Help 1] > > > If I add -X to the end of my mvn command, I see this error often: > > Received fatal alert: handshake_failure > > > Googling around, might be a TLS mismatch issue. Is there anyway to tell and > correct it? > > > I've tried to add the following tag to my settings.xml, > true and get the same error. > > Thanks > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible protocol error, handshake_error when using Maven
Hi, can you please write which exact version of the JDK you are using? Furthermore the Maven version you are using a bit out of time... Simplest try would be to upgrade to most recent version of Maven... Kind regards Karl Heinz Marbaise On 28.01.22 18:08, christopher.mil...@gd-ms.com wrote: Using Maven 3.5.4 on RHEL 8.1 with OpenJDK 1.8. I've been using maven okay for awhile now and now I'm getting the following error when running a pom.xml file. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.4:jar (default-jar) on project SOFTWARE_Build_Media: Execution default-jar of goal org.apache.maven.plugins:maven-jar-plugin:2.4:jar failed: Plugin org.apache.maven.plugins:maven-jar-plugin:2.4 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-jar-plugin:jar:2.4 -> org.apache.maven:maven-archiver:jar:2.5: Failed to read artifact descriptor for org.apache.maven:maven-archiver:jar:2.5: Could not transfer artifact org.apache.maven:maven-archiver:pom:2.5 from/to central (https://repo.maven.apache.org/maven2): Received fatal alert: handshake_failure -> [Help 1] If I add -X to the end of my mvn command, I see this error often: Received fatal alert: handshake_failure Googling around, might be a TLS mismatch issue. Is there anyway to tell and correct it? I've tried to add the following tag to my settings.xml, true and get the same error. Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible protocol error, handshake_error when using Maven
christopher.mil...@gd-ms.com wrote: > Using Maven 3.5.4 on RHEL 8.1 with OpenJDK 1.8. > > I've been using maven okay for awhile now and now I'm getting the following > error when running a pom.xml file. > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-jar-plugin:2.4:jar (default-jar) on project > SOFTWARE_Build_Media: Execution default-jar of goal > org.apache.maven.plugins:maven-jar-plugin:2.4:jar failed: Plugin > org.apache.maven.plugins:maven-jar-plugin:2.4 or one of its dependencies > could not be resolved: Failed to collect dependencies at > org.apache.maven.plugins:maven-jar-plugin:jar:2.4 -> > org.apache.maven:maven-archiver:jar:2.5: Failed to read artifact descriptor > for org.apache.maven:maven-archiver:jar:2.5: Could not transfer artifact > org.apache.maven:maven-archiver:pom:2.5 from/to central > (https://repo.maven.apache.org/maven2): Received fatal alert: > handshake_failure -> [Help 1] > > > If I add -X to the end of my mvn command, I see this error often: > > Received fatal alert: handshake_failure > > > Googling around, might be a TLS mismatch issue. Is there anyway to tell and > correct it? > > > I've tried to add the following tag to my settings.xml, > true and get the same error. Just some things to try and some questions: Can you reproduce this error when just fetching that dependency by running this command? mvn dependency:get -Dartifact=org.apache.maven.plugins:maven-jar-plugin:2.4:jar If this fails, does it work when you use Maven 3.8.4? curl https://downloads.apache.org/maven/maven-3/3.8.4/binaries/apache-maven-3.8.4-bin.tar.gz | tar -xz ./apache-maven-3.8.4/bin/mvn dependency:get -Dartifact=org.apache.maven.plugins:maven-jar-plugin:2.4:jar This works fine for me on macOS 12.2 with Maven 3.8.4 and Azul Zulu OpenJDK 8u322. According to sslscan repo.maven.apache.org only supports TLS 1.2 connections. If you are getting TLS handshake errors, then I suspect that something in your stack does not support TLS 1.2, or maybe there is an issue with the trusted CA certificates. As far as I know Java 8 should support TLS 1.2. What OpenJDK distribution and version do you use according to 'java -version'? Can you the POM file directly without Maven or Java? curl https://repo.maven.apache.org/maven2/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.pom Isn’t RHEL 8.1 also in need of an update? I believe RHEL 8.4 is current? Nils. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
