java.io.IOException

Write Channel Closed, possible SSL handshaking or trust fai lure

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 web57

  • via Unknown by 3004,
  • via Unknown by 666705,
  • via Unknown by Ramesh Hosahalli,
  • Stack trace

    • java.io.IOException: Write Channel Closed, possible SSL handshaking or trust fai lure 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(UnknownSource) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(UnknownSource) 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(UnknownSource) 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:66) 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.iom.services.validater.ejb.AddressValidater.getResponseFromWS(AddressValidater.java:246) at com.verizon.iom.services.validater.ejb.AddressValidater.validateAddress(AddressValidater.java:105) at com.verizon.iom.services.validater.ejb.ValidaterServiceBean.validateAddress(ValidaterServiceBean.java:1812) at com.verizon.iom.services.validater.ejb.ValidaterServiceBean_jf861j_EOImpl.validateAddress(ValidaterServiceBean_jf861j_EOImpl.java:98) at com.verizon.iom.services.validater.ejb.ValidaterServiceBean_jf861j_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 visitor
    Unknown visitorOnce,