79323652

Date: 2025-01-02 12:12:52
Score: 1.5
Natty:
Report link

I came across this issue as well with apache http client version 5.3.1. I enabled ssl debug logs with -Djavax.net.debug=all

and I can see it tries to close the connection and timeouts again :)

12:32:06,747 DEBUG [qtp1341085586-38] DefaultManagedHttpClientConnection - local http-outgoing-1 Close connection
javax.net.ssl|WARNING|62|qtp1341085586-38|2025-01-02 12:32:08.761 CET|SSLSocketImpl.java:1214|input stream close depletion failed (
"throwable" : {
  java.net.SocketTimeoutException: Read timed out
    at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
    at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)
    at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350)
    at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803)
    at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966)
    at java.base/java.net.Socket$SocketInputStream.read(Socket.java:961)
    at java.base/sun.security.ssl.SSLSocketInputRecord.deplete(SSLSocketInputRecord.java:498)
    at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.readLockedDeplete(SSLSocketImpl.java:1210)
    at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.deplete(SSLSocketImpl.java:1184)
    at java.base/sun.security.ssl.SSLSocketImpl.bruteForceCloseInput(SSLSocketImpl.java:802)
    at java.base/sun.security.ssl.SSLSocketImpl.duplexCloseOutput(SSLSocketImpl.java:655)
    at java.base/sun.security.ssl.SSLSocketImpl.close(SSLSocketImpl.java:579)
    at org.apache.hc.core5.http.impl.io.BHttpConnectionBase.close(BHttpConnectionBase.java:256)
    at org.apache.hc.core5.http.impl.io.DefaultBHttpClientConnection.close(DefaultBHttpClientConnection.java:68)
    at org.apache.hc.client5.http.impl.io.DefaultManagedHttpClientConnection.close(DefaultManagedHttpClientConnection.java:158)
    at org.apache.hc.core5.io.Closer.close(Closer.java:48)
    at org.apache.hc.core5.io.Closer.closeQuietly(Closer.java:71)

Obviously it uses the same timeout setting here.

Anyone aware about solution to this ?

Reasons:
  • Long answer (-1):
  • Has code block (-0.5):
  • Ends in question mark (2):
  • Low reputation (1):
Posted by: Marcin Surma