Address already in use: JVM_Bind but no process is listed using port with netstat

Question

I have a java process that make use of ServerSocket API (Java 8) and bind to the local port 12000. Process runs under a Windows service Wrapper (exe4j). I have a scheduled task that runs at 4am that stop the service and restart it after a couple of seconds. That process is installed over 400 customers locations.

Everything was running smooth until about last friday. A few processes failed to restart properly at 4am. On 2 servers I was able to connect and verify, the restart failed with both a "Address already in use: JVM_Bind". It's seems that the port 12000 was still in use by a the system.

I used every tools (processexplorer, tcpview, netstat -ano, name it) I know to try to find the process... with no success. Only a machine reboot fixed the issue. But problem came back a night or two later.

After some reading, I saw that I was doing a sockect.accept() with infinite timeout so I changed it for socket.setSoTimeout(15000); socket.accept(); instead.

I putted the new version in place but the problem is still there.

Machines got Windows updates. I did tests with the same Windows version fully updated but I can't reproduce.

I'm out of solution now.

Any ideas Thanks

Can you guarantee the service has stopped properly when told to stop? — Compass, Jul 19 '18 at 18:34
@Compass The process is no longer listed in Task Manager nor ProcessExplorer. I also get my last log message 2018-07-19 04:05:02,875 [main] INFO CommunicationCoreServer - has shut down. — sbrisson, Jul 19 '18 at 18:45
@EJP I had read that we should never do a infinite timeout on accept. Somebody saw issues (socket remained opened) with multi-core processors and infinite accept on socket. — sbrisson, Jul 19 '18 at 18:53
@EJP Did a lot of search. Can't find back the link. Anyway, I agree that it shouldn't be related to the issue. It did not fixed the problem anyway. — sbrisson, Jul 19 '18 at 19:13

score 2 · Accepted Answer · answered Aug 28 '18 at 13:54

2

A windows update affected the release of address/port after process shutdown.

Refer to Address Bind exception in Tomcat for solution.

answered Aug 28 '18 at 13:54

sbrisson

346
1
9

Updating windows 7, as per the linked answer, solved our problem too. Thank you – sergioFC Feb 01 '20 at 17:50

score 1 · Answer 2 · answered Aug 03 '18 at 09:30

I am on the same problem here. I've got several Java instances running as servers but as soon as any of those Java applications is killed and restarted then they fail to do so complaining that the port is still in use. Never happened before and I used to restart them every now and then.

My Windows server machine also received some new updates a few days ago.

By the way, I am using a tool to monitor ports and applications and those ports are not being used by any program, so the application is actually killed.

Did you found a solution ? Or maybe which Windows KB cause the issue ? — sbrisson, Aug 23 '18 at 14:03

Address already in use: JVM_Bind but no process is listed using port with netstat

2 Answers2

Linked