Encountering a java.net.SocketException: No such file or directory

Tool Version
IntelliJ Platform Gradle Plugin 2.1.0

While running my plugin as an extension in IntelliJ 2025.1, I’m encountering a java.net.SocketException. This doesn’t cause any failures, but I do see it in the terminal.

Does anyone know why this might be happening?

Fyi, this exception doesn’t occur in IntelliJ 2024.3.
Also there are no errors while building the plugin with 2025.1—it runs fine.
Attaching the exception log below.

io.netty.channel.AbstractChannel$AnnotatedSocketException: No such file or directory: /var/folders/gp/4gy_4tbn2n94_zv1ls1lcbc40000gn/T/jb.station.username.sock
Caused by: java.net.SocketException: No such file or directory
	at java.base/sun.nio.ch.UnixDomainSockets.connect0(Native Method)
	at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:166)
	at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:162)
Caused by: java.net.SocketException: No such file or directory

	at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:878)
	at io.netty.util.internal.SocketUtils$3.run(SocketUtils.java:91)
	at io.netty.util.internal.SocketUtils$3.run(SocketUtils.java:88)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:571)
	at io.netty.util.internal.SocketUtils.connect(SocketUtils.java:88)
	at io.netty.channel.socket.nio.NioDomainSocketChannel.doConnect(NioDomainSocketChannel.java:318)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.connect(AbstractNioChannel.java:295)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.connect(DefaultChannelPipeline.java:1289)
	at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:655)
	at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:634)
	at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.connect(CombinedChannelDuplexHandler.java:495)
	at io.netty.channel.ChannelOutboundHandlerAdapter.connect(ChannelOutboundHandlerAdapter.java:51)
	at io.netty.channel.CombinedChannelDuplexHandler.connect(CombinedChannelDuplexHandler.java:296)
	at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:657)
	at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:634)
	at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:618)
	at io.netty.channel.DefaultChannelPipeline.connect(DefaultChannelPipeline.java:927)
	at io.netty.channel.Channel.connect(Channel.java:297)
	at io.netty.bootstrap.Bootstrap$3.run(Bootstrap.java:264)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:148)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:141)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:521)
	at io.netty.channel.SingleThreadIoEventLoop.run(SingleThreadIoEventLoop.java:160)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:1123)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:1583)

For now you can safely ignore this.

1 Like

It is fixed for next 2015.1 EAP release already.

1 Like

Thank you @yann.cebron