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

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 846231, 1 year ago
Error writing to socket caused by: A file or directory in the path name does not exist.
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.(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)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.