java.net.ConnectException: Cannot connect to socket caused by: No such file or directory

Oracle Community | makjason | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    CC&B Install issue:ClassNotFound RPCRouterServlet & libcobjvm_sun_150

    Oracle Community | 6 years ago | makjason
    java.net.ConnectException: Cannot connect to socket caused by: No such file or directory
  2. 0

    Unable to start Weblogic in ORMB 2.3.0.1

    Oracle Community | 2 years ago | md.mujeeb
    java.net.ConnectException: Cannot connect to socket '/u01/ORMB_APPLICATION/DEMO/runtime/splSock7306' caused by: 2 No such file or directory
  3. 0

    Problem with deploying SPLService (CC&B2.2.0) on OAS

    Oracle Community | 8 years ago | 682079
    java.net.ConnectException: Error: Could not open pipe caused by system error: cannot find the file specified.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.net.ConnectException

      Cannot connect to socket caused by: No such file or directory

      at com.splwg.base.support.cobol.host.sockets.UnixDomainSocketNative.connectDomainSocket()
    2. com.splwg.base
      RotatingCommandRunnerProvider$ConnectionMonitor.run
      1. com.splwg.base.support.cobol.host.sockets.UnixDomainSocketNative.connectDomainSocket(Native Method)
      2. com.splwg.base.support.cobol.host.sockets.UnixDomainSocket.connectDomainSocket(UnixDomainSocket.java:87)
      3. com.splwg.base.support.cobol.host.sockets.UnixDomainSocketStrategy.openSocket(UnixDomainSocketStrategy.java:40)
      4. com.splwg.base.support.cobol.host.SocketStrategy.unsafeOpen(SocketStrategy.java:119)
      5. com.splwg.base.support.cobol.host.SocketStrategy.open(SocketStrategy.java:104)
      6. com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.createNewHolder(OptimizedRemoteExecuterStub.java:169)
      7. com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.getStreamHolder(OptimizedRemoteExecuterStub.java:132)
      8. com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:52)
      9. com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:111)
      10. com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.createRemoteRunner(RemoteJVMConnectionImpl.java:157)
      11. com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.<init>(RemoteJVMConnectionImpl.java:76)
      12. com.splwg.base.support.cobol.host.RemoteJVMFactoryImpl.addConnection(RemoteJVMFactoryImpl.java:89)
      13. com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.addNecessaryConnections(RotatingCommandRunnerProvider.java:401)
      14. com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.doHousekeeping(RotatingCommandRunnerProvider.java:330)
      15. com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.run(RotatingCommandRunnerProvider.java:323)
      15 frames
    3. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
      2. java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
      3. java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
      4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
      5. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:146)
      6. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:170)
      7. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
      8. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
      9. java.lang.Thread.run(Thread.java:595)
      9 frames