JDK-8132455 : [TEST_BUG] com/sun/jndi/ldap/LdapTimeoutTest.java fails at handleNamingException
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 9,9-repo-jigsaw
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2015-07-28
  • Updated: 2017-11-29
  • Resolved: 2015-11-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9
8u152Fixed 9 b93Fixed
Related Reports
Duplicate :  
Relates :  
Description
com/sun/jndi/ldap/LdapTimeoutTest.java fails in jigsaw nightly tesing:

----------System.out:(16/849)----------
Running connect timeout test with 20s kill switch
Running read timeout test with 10ms connect timeout & 20s kill switch
Running read timeout test with 20s kill switch
Running connect timeout test with 10ms connect timeout, 3000ms read timeout
Running read timeout test with 10ms connect timeout, 3000ms read timeout
Running connect timeout test with 10ms connect timeout
Running simple auth connection test
class ReadServerNoTimeoutTest - elapsed: 20201
class DeadServerNoTimeoutTest - elapsed: 20203
class ReadServerNoTimeoutTest - elapsed: 20201
class DeadServerTimeoutTest - elapsed: 212
class DeadServerTimeoutTest - elapsed: 214
class DeadServerTimeoutTest - elapsed: 212
class ReadServerTimeoutTest - elapsed: 3207
Running connect timeout test with 10ms connect timeout, 3000ms read timeout & SSL
class DeadServerTimeoutSSLTest - elapsed: 558
----------System.err:(16/936)----------
java.lang.RuntimeException: Test failed
	at LdapTest.fail(LdapTimeoutTest.java:84)
	at DeadServerTimeoutSSLTest.handleNamingException(LdapTimeoutTest.java:235)
	at LdapTest.call(LdapTimeoutTest.java:130)
	at LdapTimeoutTest.main(LdapTimeoutTest.java:455)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(java.base@9.0/Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(java.base@9.0/NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9.0/DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(java.base@9.0/Method.java:502)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92)
	at java.lang.Thread.run(java.base@9.0/Thread.java:746)

JavaTest Message: Test threw exception: java.lang.RuntimeException: Test failed
Comments
So the exception appears to be due to an unexpected early return from a read() call. This is odd as the "server" side of the test shouldn't close the connection, but apparently that is whats happening. Since this is intermittent and doesn't happen across all platforms I'm going to push a fix under this id to silence this failure for now and investigate the early closure under JDK-8141370.
11-11-2015

Hi Amy, I've just added some extra diagnostics for this test via JDK-8046768. DeadServerTimeoutSSLTest and ReadServerTimeoutTest seem to be the ones causing trouble. I've loosened up ReadServerTimeoutTest a bit but if it fails again I'm just going to remove it. With DeadServerTimeoutSSLTest we seem to be getting an unexpected exception which I then swallow. I've changed that so at least we'll know the cause on future runs. If you see it failing again please post the failure here.
25-08-2015

I ran this test with jake today and I don't see this issue. Is it possible that the original timeout was intermittent?
25-08-2015

Vinnie - would you mind have a quick look at what this might be timing out in jake and not jdk9/dev? We seem to be pick this issue when we sync up jake to jdk9-b74.
29-07-2015