I've seen this on Windows boxes, I don't know for certain about Unix. Basically, either the VM or the operating system -- I'm not sure which -- is not closing the port immediately. There's no workaround to my knowledge. I suggest a combined strategy of (1) don't close a connection until you're really really sure you don't need it anymore; and (2) provide the ability to connect on alternative ports.

-Thomas

Seems strange to me...
please check if the socket is really closed using the

aSocket.isClosed()

method.

EyeDentity