java.io.IOException

Write Channel Closed, possible SSL handshaking or trust failure

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 web9141

  • via Google Groups by Mark, 1 month ago
    Write Channel Closed, possible SSL handshaking or trust failure
  • via Google Groups by Chandra Sekhar Rao, 1 month ago
    Write Channel Closed, possible SSL handshaking or trust failure
  • via Google Groups by Ramesh Hosahalli, 1 month ago
    Write Channel Closed, possible SSL handshaking or trust failure
  • Stack trace

    • java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure at com.certicom.tls.record.WriteHandler.write(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.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:89) at weblogic.webservice.tools.wsdlp.WSDLParser.<init>(WSDLParser.java:65) at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:108) at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:84) at weblogic.webservice.core.rpc.ServiceImpl.getWebService(ServiceImpl.java:97) at weblogic.webservice.core.rpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:41) at com.verizon.wholesale.aifp.getCSRClient.<init>(getCSRClient.java:55) at com.verizon.wholesale.aifp.getCSRClient.main(getCSRClient.java:147) at com.verizon.wholesale.aifp.AIFPBean.getVBILLInfo(AIFPBean.java:344) at com.verizon.wholesale.aifp.AIFPBean.getResults(AIFPBean.java:127) at com.verizon.wholesale.aifp.AIFPBean_1720i_EOImpl.getResults(AIFPBean_1720i_EOImpl.java:46) at com.verizon.wholesale.aifp.AIFPBean_1720i_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:441) at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:382) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:726) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:377) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

    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, 1 year ago