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

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 makjason, 1 year ago
Cannot connect to socket caused by: No such file or directory
via Oracle Community by md.mujeeb, 1 year ago
Cannot connect to socket '/u01/ORMB_APPLICATION/DEMO/runtime/splSock7306' caused by: 2 No such file or directory
java.net.ConnectException: Cannot connect to socket caused by: No such file or directory
at com.splwg.base.support.cobol.host.sockets.UnixDomainSocketNative.connectDomainSocket(Native Method)
at com.splwg.base.support.cobol.host.sockets.UnixDomainSocket.connectDomainSocket(UnixDomainSocket.java:87)
at com.splwg.base.support.cobol.host.sockets.UnixDomainSocketStrategy.openSocket(UnixDomainSocketStrategy.java:40)
at com.splwg.base.support.cobol.host.SocketStrategy.unsafeOpen(SocketStrategy.java:119)
at com.splwg.base.support.cobol.host.SocketStrategy.open(SocketStrategy.java:104)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.createNewHolder(OptimizedRemoteExecuterStub.java:169)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.getStreamHolder(OptimizedRemoteExecuterStub.java:132)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:52)
at com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:111)
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:89)
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:417)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:146)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:170)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

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