On 4/15/22 9:39 AM, Jack Woehr wrote:
Not sure about the particular pathology in this instance, but it's theJava
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
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.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.