java.io.IOException

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

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 web32278

  • via Oracle Community by 846231, 11 months ago
    Error writing to socket caused by: A file or directory in the path name does not exist.
  • via Jenkins JIRA by Fred G, 1 year ago
    error=2, A file or directory in the path name does not exist.
  • via Oracle Community by nww, 1 year ago
    error=2, A file or directory in the path name does not exist.
  • Stack trace

    • 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(Native Method) at com.splwg.base.support.cobol.host.sockets.UnixDomainSocket.writeBuffer(UnixDomainSocket.java:64) at com.splwg.base.support.cobol.host.sockets.PipeSocket.writeBuffer(PipeSocket.java:113) at com.splwg.base.support.cobol.host.sockets.PipeSocket$PipeOutputStream.writeBufferAndClear(PipeSocket.java:279) at com.splwg.base.support.cobol.host.sockets.PipeSocket$PipeOutputStream.flush(PipeSocket.java:307) at java.io.DataOutputStream.flush(DataOutputStream.java:131) at com.splwg.base.support.cobol.host.OptimizedDataOutput.flush(OptimizedDataOutput.java:55) at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80) at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:58) at com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:109) at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.createRemoteRunner(RemoteJVMConnectionImpl.java:157) at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.<init>(RemoteJVMConnectionImpl.java:76) at com.splwg.base.support.cobol.host.RemoteJVMFactoryImpl.addConnection(RemoteJVMFactoryImpl.java:80) at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.addNecessaryConnections(RotatingCommandRunnerProvider.java:401) at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.doHousekeeping(RotatingCommandRunnerProvider.java:330) at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.run(RotatingCommandRunnerProvider.java:323) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:432) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:295) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:80) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:157) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:810)

    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

    You’re the first here who have seen this exception.