JDK-8325384 : sun/security/ssl/SSLSessionImpl/ResumptionUpdateBoundValues.java failing intermittently when main thread is a virtual thread
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Affected Version: 23
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-02-07
  • Updated: 2024-08-09
  • Resolved: 2024-05-16
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 17 JDK 21 JDK 23
17.0.13Fixed 21.0.5-oracleFixed 23 b24Fixed
Related Reports
Relates :  
JDK-8215933 - TLS Session Resumption loses track of SSLSession values
Description
This test fails intermittently when run with JTREG_TEST_THREAD_FACTORY=Virtual, meaning the main thread is a virtual thread.

java.lang.RuntimeException: 'trigger new session ticket' missing from stdout/stderr
	at jdk.test.lib.process.OutputAnalyzer.shouldContain(OutputAnalyzer.java:252)
	at ResumptionUpdateBoundValues.main(ResumptionUpdateBoundValues.java:196)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.VirtualThread.run(VirtualThread.java:329)
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk17u-dev/pull/2610 Date: 2024-06-19 05:07:24 +0000
08-08-2024
In 17u we don't have virtual threads and it was not backported there by Oracle. However, it's test-only and the code change could make sense anyway, so approving.
24-06-2024
[jdk17u-fix-request] Approval Request from Amos "Backporting. No risk, test fix. Clean backport. Test passes and SAP nightlies pass on 2024-06-20”
20-06-2024
[jdk21u-fix-request] Approval Request from Amos "Backporting for parity with 21.0.5-oracle. No risk, test fix. Clean backport. Test passes and SAP nightlies pass on 2024-06-21”
20-06-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk21u-dev/pull/756 Date: 2024-06-19 05:07:30 +0000
19-06-2024
Changeset: da9c23ac Author: Mark Powers <mpowers@openjdk.org> Date: 2024-05-16 17:07:19 +0000 URL: https://git.openjdk.org/jdk/commit/da9c23ace9bdf398d811a88ed137217dd3167231
16-05-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/19160 Date: 2024-05-09 19:02:05 +0000
09-05-2024
No luck with remote-test. All 20 test repetitions passed.
19-04-2024
Mach5 history I shows six CI tasks with this failure and with log files. Log files for personal tasks are long gone since they are only retained for one month. All six tasks contain "jdk-23-loom" in their Task Id. [~alanb] I'm assuming there is something special about "jdk-23-loom" that contributed to the failure. Where can I find this code?
18-04-2024
How intermittent? I tried remote-build-and-test and remote-test with --test-repeat 20 and didn't see any failure.
08-04-2024