- 
    Bug 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    8, 11, 17
- 
        b18
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8266366 | 11.0.13-oracle | Thejasvi Voniadka | P4 | Resolved | Fixed | b01 | 
| JDK-8266478 | 11.0.12 | Rajan Halade | P4 | Resolved | Fixed | b01 | 
| JDK-8266367 | 8u311 | Thejasvi Voniadka | P4 | Resolved | Fixed | b01 | 
                    Occasional interop tests failures may occur when making use of the test/jdk/javax/net/ssl/TLSCommon/interop framework since there is no assurance the selected available port it is still free at the time a non JDK server starts, for example, by command line. To mitigate intermittent failures, the test/jdk/javax/net/ssl/TLSCommon/interop/BaseInteropTest.java should first validate the server is alive and if not, retry to create a valid server.
In addition, Utilities::isSessionResumed implementation is not correct, it is more accurate to compare creation time of first and second session instead of comparing the second session with a manually obtained current time, that could result in a misleading error.
In addition, Utilities::isSessionResumed implementation is not correct, it is more accurate to compare creation time of first and second session instead of comparing the second session with a manually obtained current time, that could result in a misleading error.
- backported by
- 
                    JDK-8266366 Harden TLS interop tests -           
- Resolved
 
-         
- 
                    JDK-8266367 Harden TLS interop tests -           
- Resolved
 
-         
- 
                    JDK-8266478 Harden TLS interop tests -           
- Resolved
 
-         
 
        