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

On 4/15/22 9:54 AM, Jim Oberholtzer wrote:

On a modern system if you're contemplating stopping/starting TCP you might
just as well IPL. Seems like using a nuke when a 100# bomb might work
though.

Looking at the QSYSOPR messages, I see that the system was taken down to restricted condition at 01:04 this morning, system time, for a backup, which completed at 02:03, with the subsystems, and TCP, starting.

Looking at catalina.out for *YESTERDAY* shows Tomcat being shut down at 01:04 yesterday morning, and coming back up at 02:04 that morning, without incident.

Today, however, catalina.out shows the same thing up to the point where 8005 shows up as unavailable.

Looking back at the QSYSOPR messages, I see TWO OVERLAPPING STRTCPs, initiated within seconds of each other. That doesn't make any sense to me. And yet I see it happening every day this week.

So far, nothing is making any sense. TCP can't be in *that bad* of a shape, since I'm able to get terminal sessions via TN5250. And WRKTCPSTS shows 59 servers waiting for connections, and 61 established connections.

--
JHHL