On Windows we recently run into this error rather often in the test LdapPoolTimeoutTest.java :

MSG RTE: javax.naming.CommunicationException: example.com:1234 [Root exception is java.net.ConnectException: Connection timed out: no further information]
MSG: Connect timed out
MSG: Timeout exceeded while waiting for a connection: 26984ms
MSG: Timed out waiting for lock
MSG: Timed out waiting for lock
MSG: Timed out waiting for lock
MSG: Timeout exceeded while waiting for a connection: 26984ms
MSG: Timeout exceeded while waiting for a connection: 26984ms
java.lang.Exception: failures: 1
at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:104)
at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:58)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
at java.base/java.lang.Thread.run(Thread.java:1570)

Can we extend the accepted exception message strings to 'ConnectException: Connection timed out' ?
Additionally the 'Connection timed out: no further information' is far from perfect, should we add some text explaining what went wrong?
(probably some socket/networking operation from Net.c)