java.lang.Throwable

Stack trace

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web111

  • via Unknown by 666705,
  • via Unknown by Mark,
  • via Unknown by 3004,
  • Stack trace

    • java.lang.Throwable: Stack trace at weblogic.security.utils.SSLSetup.debug(SSLSetup.java:265) at com.certicom.tls.record.alert.Alert.<init>(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 com.certicom.net.ssl.HttpsClient.doHandshake(Unknown Source) at com.certicom.net.ssl.internal.HttpURLConnection.getInputStream(Unknown Source) at weblogic.webservice.client.https.HttpsURLConnection.getInputStream(HttpsURLConnection.java:216) at weblogic.webservice.tools.wsdlp.DefinitionFactory.createDefinition(DefinitionFactory.java:87) at weblogic.webservice.tools.wsdlp.WSDLParser.<init>(WSDLParser.java:76) at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:108) at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:84) at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:79) at webservices.generated.ServicesBean_Impl.<init>(ServicesBean_Impl.java:22) at WSDLTest.main(WSDLTest.java:12)

    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

    We couldn't find other users who have seen this exception.