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.
(although I haven't a clue how that can even be done on a box that
presumably isn't old enough to have Twinax).
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.