RFR [testbug]: 8250772: Test com/sun/jndi/ldap/NamingExceptionMessageTest.java fails intermittently with javax.naming.ServiceUnavailableException
Hi, Please, help to review NamingExceptionMessageTest test stabilization change: There is a race condition between the closure of connection in test LDAP server and the JDKs LDAP client code. Due to this race the test could generate ServiceUnavailableException instead of the required NamingException. Webrev: http://cr.openjdk.java.net/~aefimov/8250772/00/index.html JBS: https://bugs.openjdk.java.net/browse/JDK-8250772 The following modifications have been made to the test code: a) To increase the reproduction rate of the required exception message the connection closure timeout has been added to the test LDAP server's BIND operation handler b) ServiceUnavailableException is now treated as an acceptable exception The modified test was successfully executed 100+ times alongside to other LDAP tests With Best Regards, Aleksei
Hi Aleksei, I agree that this is the best fix for this issue. best regards, -- daniel On 06/08/2020 23:21, Aleks Efimov wrote:
Hi,
Please, help to review NamingExceptionMessageTest test stabilization change: There is a race condition between the closure of connection in test LDAP server and the JDKs LDAP client code. Due to this race the test could generate ServiceUnavailableException instead of the required NamingException.
Webrev: http://cr.openjdk.java.net/~aefimov/8250772/00/index.html JBS: https://bugs.openjdk.java.net/browse/JDK-8250772
The following modifications have been made to the test code: a) To increase the reproduction rate of the required exception message the connection closure timeout has been added to the test LDAP server's BIND operation handler b) ServiceUnavailableException is now treated as an acceptable exception
The modified test was successfully executed 100+ times alongside to other LDAP tests
With Best Regards, Aleksei
participants (2)
-
Aleks Efimov
-
Daniel Fuchs