javax.net.ssl.SSLKeyException

FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web227

  • FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
  • via Google Groups by Gaurav Khanna, 1 month ago
    FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
  • via Google Groups by Mark, 1 month ago
    FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
  • Stack trace

    • javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received. at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source) at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source) at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source) at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source) at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source) at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source) at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source) at com.certicom.tls.record.WriteHandler.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:110) at java.io.FilterOutputStream.write(FilterOutputStream.java:80) at weblogic.webservice.binding.soap.HttpClientBinding.writeToStream(HttpClientBinding.java:405) at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBinding.java:196) at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHandler.java:37) at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:143) at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231) at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443) at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:290) at weblogic.jws.proxies.HelloWorldSecureSoap_Stub.clientRequestwithReturn(HelloWorldSecureSoap_Stub.java:26) at weblogic.jws.proxies.HelloWorldSecureSoap_Stub.clientRequestwithReturn(HelloWorldSecureSoap_Stub.java:46) at security.SSL.SSLClient.SSLClient.main(SSLClient.java:51)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    5 more bugmates