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 3004, 1 year ago
FATAL Alert: BAD_CERTIFICATE - A corrupt or unusable certificate was received
via middlewaremagic.com by Unknown author, 1 year ago
[Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 – 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
via Oracle Community by 525098, 9 months ago
[Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected. NMProcess:
via Coderanch by preeti vivek gupta, 1 year ago
[Security:090477]Certificate chain received from www.googleapis.com - 74.125.93.95 was not trusted causing SSL handshake failure.
via weblogic-wonders.com by Unknown author, 1 year ago
[Security:090477]Certificate chain received from servicemngr-pt168.tsl.telus.com – x.y.z.l was not trusted causing SSL handshake failure.
via weblogic-wonders.com by Unknown author, 2 years ago
[Security:090477]Certificate chain received from servicemngr-pt168.tsl.telus.com – x.y.z.l was not trusted causing SSL handshake failure.
javax.net.ssl.SSLKeyException: FATAL Alert: BAD_CERTIFICATE - A corrupt or unusable
certificate was received	at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(UnknownSource)