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

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.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Fri, Apr 15, 2022 at 11: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.

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. No joy.

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). And if that doesn't work,
re-IPL the system.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com