Caused by: java io eofexception SSL peer shut down incorrectly spring boot

59

New! Save questions or answers and organize your favorite content.
Learn more.

I need to make a request through a HTTPS protocol. I wrote the following code:

I got this exception stacktrace with a java.io.EOFException:

I got successful response from https://google.com but this error from URL above (https://ancine.band.com.br/xml/pgrt1_dta_20150303.xml).

Using PHP, .NET and NodeJS that URL works fine.

Anyone has any idea why this happening?

asked Mar 6, 2015 at 22:34

3

That is a problem of security protocol. I am using TLSv1 but the host accept only TLSv1.1 and TLSv1.2 then I changed the protocol in Java with the instruction below:

System.setProperty("https.protocols", "TLSv1.1");

answered Mar 10, 2015 at 14:54

anetoaneto

1,4312 gold badges13 silver badges19 bronze badges

2

You can set protocol versions in system property as :

overcome ssl handshake error

answered Mar 5, 2018 at 9:48

Zigri2612Zigri2612

2,18919 silver badges32 bronze badges

Apart from the accepted answer, other problems can cause the exception too. For me it was that the certificate was not trusted (i.e., self-signed cert and not in the trust store).

If the certificate file does not exists, or could not be loaded (e.g., typo in path) can---in certain circumstances---cause the same exception.

answered Sep 26, 2016 at 12:26

D. KovácsD. Kovács

1,22212 silver badges22 bronze badges

5

As @Zigri2612 suggested, what worked for me was to add TLS https.protocols, but i had to do it with white spaces instead of comma separated values:

answered Oct 27, 2021 at 14:30

This error is generic of the security libraries and might happen in other cases. In case other people have this same error when sending emails with javax.mail to a smtp server. Then the code to force other protocol is setting a property like this:

answered Nov 17, 2018 at 10:00

jolumgjolumg

6942 gold badges15 silver badges30 bronze badges

please close the android studio and remove the file

and

file form your project .Hope so it is helpful

Location:Go to Android studio projects->your project ->see both file remove (.gradle & .idea)

answered Oct 27, 2020 at 6:03

Below code worked for me You have to add below configuration in surefire plugin

<configuration> <argLine>-Dhttps.protocols=TLSv1.1</argLine> </configuration>

answered Jul 8, 2021 at 13:40

I was facing same issue, for me adding certificate to trust store solved this issue.

answered Mar 14, 2018 at 3:29

AliAli

1,3702 gold badges19 silver badges29 bronze badges

I had a similar issue that was resolved by unchecking the option in java advanced security for "Use SSL 2.0 compatible ClientHello format.

answered Sep 6, 2018 at 17:47

DylanDylan

2,0151 gold badge25 silver badges44 bronze badges

The accepted answer didn't work in my situation, not sure why. I switched from JRE1.7 to JRE1.8 and that resolved the issue automatically. JRE1.8 uses TLS1.2 by default

answered Dec 5, 2018 at 19:12

Sam GhSam Gh

4906 silver badges10 bronze badges

I experienced this exception using a SSL/TLS server Socket library on java 8. Updating the jdk to 14 (and also the VM to 14) solved the issue.

answered Aug 10, 2020 at 23:54

BogdanBogdan

1163 bronze badges

I was having the same issue, as everyone else I suppose.. adding the System.setProperties(....) didn't fix it for me.

So my email client is in a separate project uploaded to an artifactory. I'm importing this project into other projects as a gradle dependency. My problem was that I was using implementation in my build.gradle for javax.mail, which was causing issues downstream.
I changed this line from implementation to api and my downstream project started working and connecting again.

answered Aug 27, 2020 at 21:00

I had mutual SSL enabled on my Spring Boot app and my Jenkins pipeline was re-building the dockers, bringing the compose up and then running integration tests which failed every time with this error. I was able to test the running dockers without this SSL error every time in a standalone test on the same Jenkins machine. It turned out that server was not completely up when the tests started executing. Putting a sleep of few seconds in my bash script to allow Spring boot application to be up and running completely resolved the issue.

answered Jan 3, 2021 at 12:53

TechFreeTechFree

2,3741 gold badge13 silver badges17 bronze badges

In my case i was making a request to a system that is using SSLV3. So i have added the following jvm option. And problem got resolved.

answered Jun 10, 2021 at 9:58

Sometimes it can be caused due to network issue. Don't know the reason but after switching to other network, the application got build and installed successfully.

answered Jul 3, 2021 at 4:10

VivekVivek

4204 silver badges5 bronze badges

For me, setting -Dhttps.protocols="TLSv1,TLSv1.1,TLSv1.2" (or -Dhttps.protocols="TLSv1.2" for that matter) didn't work.

Since I was running the problematic code in a Docker container in an AWS K8S cluster, I found a similar solution in the [AWS Documentation][1] After setting this system property -Djdk.tls.client.protocols=TLSv1.2, the error was gone.

[UPDATE] After deploying this to production, I noticed the behaviour is intermittent: sometimes I emails were getting sent, sometimes they didn't. Whilst researching some more, I found that my client was using TLS 1.0 which the server didn't support (it only supported TLS 1.2) The verbose error messages I was getting is this:

javax.net.ssl|SEVERE|10|grpc-default-executor-0|2021-10-22 19:38:48.017 GMT|Logger.java:765|Fatal (HANDSHAKE_FAILURE): Couldn't kickstart handshaking

Finally, after multiple trials, I solved it using the answer from here: How to force JavaMailSenderImpl to use TLS1.2? [1]: https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/security-java-tls.html

answered Oct 22, 2021 at 14:43

0

I've encountered the same error message but the reason and solution are quite interesting:

my problem resolved by upgrade the openjdk from 8u40 to 8u191 or higher version 8u312,

the root cause is a kind of interoperability issue that seems the client and server are using different padding method or cipher parameter(e.g EC curve) for DH key exchange,

so if you run out of solutions, probably you may try upgrade your jdk(don't just upgrade to a major version, try to upgrade to a higher minor version first, please note my problem resolved by higher minor version for openjdk8uXXX but still failed with openjdk9)

you may refer to the whole troubleshooting process at(handshake section): https://lyhistory.github.io/docs/software/network/http_ssl_tls_setup.html

answered Feb 4 at 10:30

LIU YUELIU YUE

1,31710 silver badges16 bronze badges

For my Spring Boot API consuming app, this issue was caused by being connected to a VPN.

I tried various work arounds including the accepted answer (I called System.setProperty("https.protocols", "TLSv1.1") in my main function) but nothing worked.

I disconnected from the VPN and no longer got this error.

answered Sep 19 at 6:19

Check your internet connection, then resync your project.

answered Jan 31 at 12:01