Tomcat 8.5.73 not coming up on customer box. "Bind failed."

This morning, I arrived at work to find that a customer was complaining about their Tomcat server (running on an IBM Midrange box).

It had locked up last night, while being shut down, and now, if you try to start it, it fails with

15-Apr-2022 10:35:34.867 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8005]:
java.net.BindException: The socket name is not available on this system. (Bind failed)  at java.net.PlainSocketImpl.socketBind(Native Method)  at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:417) at java.net.ServerSocket.bind(ServerSocket.java:444) at java.net.ServerSocket.<init>(ServerSocket.java:258) at org.apache.catalina.core.StandardServer.await(StandardServer.java:414) at org.apache.catalina.startup.Catalina.await(Catalina.java:776) at org.apache.catalina.startup.Catalina.start(Catalina.java:722)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

Catalina.out shows "Starting ProtocolHandler ["https-jsse-nio-443"]," then "Server startup in 20227 ms," then it blows up as above.

According to the server.xml, the only ports it is listening on are 8005 and 443. And according to a WRKTCPSTS *CNN (the AS/400 equivalent of a "super netstat"), there is nothing currently grabbing hold of either of those two ports.

Any insights as to what could be happening?

--
James H. H. Lampert
Touchtone Corporation