java.io.IOException: Error writing to socket caused by: A file or directory in the path name does not exist.

Oracle Community | 846231 | 5 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    MKSYSB for Linux

    Oracle Community | 5 years ago | 846231
    java.io.IOException: Error writing to socket caused by: A file or directory in the path name does not exist.

    Root Cause Analysis

    1. java.io.IOException

      Error writing to socket caused by: A file or directory in the path name does not exist.

      at com.splwg.base.support.cobol.host.sockets.UnixDomainSocketNative.writeToSocket()
    2. com.splwg.base
      PipeSocket$PipeOutputStream.flush
      1. com.splwg.base.support.cobol.host.sockets.UnixDomainSocketNative.writeToSocket(Native Method)
      2. com.splwg.base.support.cobol.host.sockets.UnixDomainSocket.writeBuffer(UnixDomainSocket.java:64)
      3. com.splwg.base.support.cobol.host.sockets.PipeSocket.writeBuffer(PipeSocket.java:113)
      4. com.splwg.base.support.cobol.host.sockets.PipeSocket$PipeOutputStream.writeBufferAndClear(PipeSocket.java:279)
      5. com.splwg.base.support.cobol.host.sockets.PipeSocket$PipeOutputStream.flush(PipeSocket.java:307)
      5 frames
    3. Java RT
      DataOutputStream.flush
      1. java.io.DataOutputStream.flush(DataOutputStream.java:131)
      1 frame
    4. com.splwg.base
      RotatingCommandRunnerProvider$ConnectionMonitor.run
      1. com.splwg.base.support.cobol.host.OptimizedDataOutput.flush(OptimizedDataOutput.java:55)
      2. com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80)
      3. com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:58)
      4. com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:109)
      5. com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.createRemoteRunner(RemoteJVMConnectionImpl.java:157)
      6. com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.<init>(RemoteJVMConnectionImpl.java:76)
      7. com.splwg.base.support.cobol.host.RemoteJVMFactoryImpl.addConnection(RemoteJVMFactoryImpl.java:80)
      8. com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.addNecessaryConnections(RotatingCommandRunnerProvider.java:401)
      9. com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.doHousekeeping(RotatingCommandRunnerProvider.java:330)
      10. com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.run(RotatingCommandRunnerProvider.java:323)
      10 frames
    5. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:432)
      2. java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:295)
      3. java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
      4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:80)
      5. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:157)
      6. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:181)
      7. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
      8. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
      9. java.lang.Thread.run(Thread.java:810)
      9 frames