JDK-8151678 : com/sun/jndi/ldap/LdapTimeoutTest.java failed due to timeout on DeadServerNoTimeoutTest is incorrect
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 9,10,12
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-03-11
  • Updated: 2022-08-17
  • Resolved: 2019-09-13
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 11 JDK 13 JDK 14 JDK 8 Other
11.0.9-oracleFixed 13.0.6Fixed 14 b15Fixed 8u261Fixed openjdk7uFixed
Related Reports
Duplicate :  
JDK-8214203 - com/sun/jndi/ldap/LdapTimeoutTest.java failed with timeout on (Read/Dead)ServerNoTimeoutTest is incorrect
Relates :  
JDK-8160768 - Add capability to custom resolve host/domain names within the default JNDI LDAP provider
Relates :  
JDK-8214241 - Problem list com/sun/jndi/ldap/LdapTimeoutTest.java for all platforms
Relates :  
JDK-8194662 - Problem list com/sun/jndi/ldap/LdapTimeoutTest.java
Description
The below is the associated logs:

DeadServerNoTimeoutTest fail: timeout should be at least 18000 ms, actual time is 278 ms
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Test failed
	at java.util.concurrent.FutureTask.report(java.base@9-ea/FutureTask.java:123)
	at java.util.concurrent.FutureTask.get(java.base@9-ea/FutureTask.java:193)
	at LdapTimeoutTest.main(LdapTimeoutTest.java:428)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
	at java.lang.Thread.run(java.base@9-ea/Thread.java:804)
Caused by: java.lang.RuntimeException: Test failed
	at LdapTest.fail(LdapTimeoutTest.java:84)
	at DeadServerNoTimeoutTest.handleNamingException(LdapTimeoutTest.java:202)
	at LdapTest.call(LdapTimeoutTest.java:134)
	at LdapTest.call(LdapTimeoutTest.java:55)
	at java.util.concurrent.FutureTask.run(java.base@9-ea/FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@9-ea/ThreadPoolExecutor.java:1158)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@9-ea/ThreadPoolExecutor.java:632)
	... 1 more


Please see the comments for more details.
Comments
Fix request (13u) I'd like to backport this fix to 13u as follow-up of JDK-8160768. The patch applies cleanly This patch is also required for clean backport of JDK-8062947
16-11-2020
Review comments addressed: http://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-September/012651.html Approving for 8u272.
09-09-2020
Spotted a few issues with the proposed patch, so pushing back to jdk8u-needs-review.
07-09-2020
Critical Fix Request (8u) I would like to backport this patch to openjdk-8u272 for parity with Oracle 8u271. The original patch does not apply cleanly. The 8u patch has been reviewed by Severin. https://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-August/012586.html This patch is a followup on JDK-8160768, which is an important backport in 8u272, we should not leave it broken.
02-09-2020
[~sgehwolf] Done. Thanks.
02-09-2020
[~zgu] Since this is a follow-up on JDK-8160768 I'd suggest to flag it jdk8u-critical-request as JDK-8160768 is in 8u272. We should get then in the same release.
02-09-2020
Fix Request (11u) I'd like to backport this fix to 11u as follow-up of JDK-8160768. Oracle have backported it to 11.0.9 as well. The patch didn't apply and manual action had to be taken. RFR thread: https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2020-August/003706.html
31-08-2020
8u code review: https://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-August/012586.html
29-08-2020
11u notice: This was brought to 11.0.9-oracle. The part fixing the test applies fine to OpenJDK 11u. The part fixing java.naming can not be brought to OpenJDK 11u currently. OpenJDK 11u lacks JDK-8160768, which introduces the code fixed here. It seems that JDK-8160768 is in 11.0.8-oracle. It is not in OpenJDK 11u though. We should address this for OpenJDK 11u once JDK-8160768 was pushed. The test fixes are not urgent as the test is ProblemListed.
03-07-2020
URL: https://hg.openjdk.java.net/jdk/jdk/rev/1def54255e93 User: prappo Date: 2019-09-13 10:01:36 +0000
13-09-2019
This test has numerous issues, it just so happens that one of them is due to JDK-8160768. The fix contains both the changes to the test and the code. Please be careful, this is NOT a "test change only". For more detail see: https://mail.openjdk.java.net/pipermail/core-libs-dev/2019-August/062089.html
04-09-2019
Previous failure on linux-x64 and recent failure observed on other platforms are all failed from : DeadServerNoTimeoutTest.handleNamingException Test is problem listed for all platforms in JDK-8214241.
23-11-2018
Test is now also being seen to fail the same way on Windows and OS X! See reports in JDK-8214203 - now closed as a duplicate of this bug.
22-11-2018
Test has been problem listed for linux-all (JDK-8194662)
08-01-2018
This test needs to be added to the problem list!
22-12-2017