java.lang.RuntimeException: Server not ready yet

JDK Bug System | Artem Smotrakov | 8 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    javax/net/ssl/Stapling/SSLSocketWithStapling.java may fails with the following output: ----------System.out:(38/1637)---------- ======================================= Stapling enabled, default configuration ======================================= PASS ======================================= ===================================== Stapling enabled, PKIXParameters with Revocation checking enabled ===================================== PASS ===================================== ======================================= Stapling enabled, default configuration ======================================= PASS ======================================= ======================================= Stapling enbled in client and server, but OCSP responders disabled. PKIXParameters with Revocation checking enabled. ======================================= PASS ======================================= [pool-17-thread-1]: Exception: java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(java.base@9-ea/Native Method) at java.net.AbstractPlainSocketImpl.bind(java.base@9-ea/AbstractPlainSocketImpl.java:437) at java.net.ServerSocket.bind(java.base@9-ea/ServerSocket.java:376) at sun.security.testlibrary.SimpleOCSPServer$2.run(SimpleOCSPServer.java:217) at java.util.concurrent.Executors$RunnableAdapter.call(java.base@9-ea/Executors.java:514) 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) at java.lang.Thread.run(java.base@9-ea/Thread.java:843) ----------System.err:(16/953)---------- Server died... Server died... java.lang.RuntimeException: Server not ready yet at SSLSocketWithStapling.testHardFailFallback(SSLSocketWithStapling.java:327) at SSLSocketWithStapling.main(SSLSocketWithStapling.java:128) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:533) at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110) at java.lang.Thread.run(java.base@9-ea/Thread.java:843)

    JDK Bug System | 8 months ago | Artem Smotrakov
    java.lang.RuntimeException: Server not ready yet

    Root Cause Analysis

    1. java.lang.RuntimeException

      Server not ready yet

      at SSLSocketWithStapling.testHardFailFallback()
    2. Unknown
      SSLSocketWithStapling.main
      1. SSLSocketWithStapling.testHardFailFallback(SSLSocketWithStapling.java:327)
      2. SSLSocketWithStapling.main(SSLSocketWithStapling.java:128)
      2 frames