I believe that you can fix this by increasing the ConnectTimeout pool. I set a very low level (10 ms), so when the pool was created, some clients could not connect in this short period. If the pool returned one of these clients, it would throw this error (port "0" - because it is not connected - it does not know which port it is not connected to). After a delay, all clients can connect.
I increased the connection timeout to 500 ms, and the problem disappeared - the clients all connected, although some of them were blocked for a couple of hundred milliseconds. But this is much better than a mistake.
source share