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

On Fri, Apr 15, 2022 at 10:48 AM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 4/15/22 9:39 AM, Jack Woehr wrote:

Not sure about the particular pathology in this instance, but it's the

Java

runtime itself telling you something already has hold of the socket, and
it's not lying.

But it could be deluded into *thinking* something already has hold of
the socket.

I have no idea how one would do that. Java just goes to native code and
accesses the C sockets library.

WRKTCPSTS shows *nothing* on 8005, 8009, 443, or 8443. I've tried
changing 8005 to 8009. No joy. I then tried changing 443 to 8443.

Without logging into your system and poking around, my easiest SWAG based
on what you reported is that every time you try to start Tomcat, somehow
you're starting 2 instances at once.

I'm seriously considering having them do an ENDTCP followed by a STRTCP

(although I haven't a clue how that can even be done on a box that
presumably isn't old enough to have Twinax).

Neither the HMC nor the LAN Console is affected by ENDTCP.