The com/sun/jndi/ldap/LdapPoolTimeoutTest.java test has been intermittently failing for several years now. The test is implemented to expect specific exception types and very specific exception messages in those exceptions. When the exception message doesn't match the expected message, the test fails with an assertion error but it doesn't include the original exception that had an unexpected message in the test failure. This makes it hard to debug the cause of the test failure.

The test can be improved to propagate the original unexpected exception so that when the test fails, the complete stacktrace is available for debugging the failure.