IJ46285: KEEPALIVECACHE BLOCKS THREADS WHILE CLOSING CONNECTIONS

APAR status

• Closed as program error.

Error description

• Error Message: N/A
  .
  Stack Trace: Exception in thread "main"
  java.util.concurrent.ExecutionException:
  java.lang.RuntimeException:Wait for second request timed out
  at
  java.base/java.util.concurrent.CompletableFuture.reportGet(Compl
  etableFuture.java:395)
  at
  java.base/java.util.concurrent.CompletableFuture.get(Completable
  Future.java:1999)
  at B8293562.clientHttpCalls(B8293562.java:111)
  at B8293562.main(B8293562.java:61)
  Caused by: java.lang.RuntimeException: Wait for second request
  timed out
  at B8293562$SlowCloseSocket.close(B8293562.java:130)
  at
  java.base/sun.net.www.http.HttpClient.closeServer(HttpClient.jav
  a:1095)
  at
  java.base/sun.net.www.http.KeepAliveCache.run(KeepAliveCache.jav
  a:235)
  at java.base/java.lang.Thread.run(Thread.java:839)
  at
  java.base/jdk.internal.misc.InnocuousThread.run(InnocuousThread.
  java:161)
  .
  

Local fix

Problem summary

• The KeepAliveCache thread closes stale sockets while holding a
  lock, this means that while it's closing connections, no other
  connections can be established/retrieved from cache/added to
  cache.
  

Problem conclusion

• connections should be closed without holding the cache lock and
  read timeout will be reset to a lower value before the
  connection is returned to the cache/closed
  .
  This APAR will be fixed in the following Releases:
  .
  IBM Semeru Runtimes
   11 11.0.17.0
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  maintenance can be found at:
   https://www.ibm.com/support/pages/java-sdk
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  OPENJDK CLASS L

• Fixed component ID

  621800100

Applicable component levels