JDK-8348326 : MultiNSTParallel fails with "'MultiNST PSK' missing from stderr"
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Affected Version: 25
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2025-01-22
  • Updated: 2025-05-27
  • Resolved: 2025-05-27
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Unfortunately the MultiNSTParallel.java test fails 1-2 times per week on some of our Linux ppc64le test machines with errors like these :

java.lang.Exception: java.lang.RuntimeException: 'MultiNST PSK' missing from stderr
at MultiNSTParallel.main(MultiNSTParallel.java:154)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
at java.base/java.lang.Thread.run(Thread.java:1447)
Caused by: java.lang.RuntimeException: 'MultiNST PSK' missing from stderr
at jdk.test.lib.process.OutputAnalyzer.stderrShouldContain(OutputAnalyzer.java:283)
at MultiNSTParallel.main(MultiNSTParallel.java:123)
... 4 more

I add a longer log part of a failing test to this JBS issue . 
Comments
JDK-8348309 fixed the issues on the testing platform.
27-05-2025

The attached log is not what I expected. The TLS server appears to be up, as it printed the server port to stderr. The initial client connection starts after that, but is printed to stdout. No threads are used in this portion of the code, so it's strange why the client error message says "socket not connected". This will require more debugging text in the test and likely printing to stderr only. Those changes will be tracked by JDK-8348309. The failure does not indicate a jdk issue. Without the initial TLS connection, the NSTs cannot be populated for the test to work.
22-01-2025