Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 970682, 1 year ago
Received fatal alert: bad_certificate
via Google Groups by Nelson Bolyard, 8 months ago
Received fatal alert: handshake_failure
via mkyong.com by Unknown author, 1 year ago
via mkyong.com by Unknown author, 1 year ago
via GitHub by feiyang
, 2 years ago
Received fatal alert: handshake_failure
via Stack Overflow by zbigh
, 2 years ago
Received fatal alert: handshake_failure
javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1806)	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:986)	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170)	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1197)	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1181)	at com.octetstring.vde.ConnectionHandler.initializeConnection(ConnectionHandler.java:174)	at com.octetstring.vde.ConnectionHandler.run(ConnectionHandler.java:218)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	at java.lang.Thread.run(Thread.java:662)