SSLSocket duplex close failed

See original GitHub issue

We have a Tomcat 8.0.x web application that uses the PostgreSQL JDBC driver. We upgraded our JDK and PostgreSQL JDBC driver recently, and our catalina.out logs now show a lot of this:

javax.net.ssl|ALL|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.377 EDT|Logger.java:765|Closing input stream
javax.net.ssl|ALL|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.396 EDT|Logger.java:765|Closing output stream
javax.net.ssl|FINE|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.396 EDT|Logger.java:765|duplex close of SSLSocket
javax.net.ssl|FINE|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.396 EDT|Logger.java:765|close the underlying socket
javax.net.ssl|FINE|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.396 EDT|Logger.java:765|close the SSL connection (initiative)
javax.net.ssl|FINE|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.396 EDT|Logger.java:765|close inbound of SSLSocket
javax.net.ssl|WARNING|0B 72|http-nio-6080-exec-334|2021-09-26 24:00:13.397 EDT|Logger.java:765|SSLSocket duplex close failed (
"throwable" : {
  java.net.SocketException: Socket is closed
        at java.net.Socket.shutdownInput(Socket.java:1539)
        at sun.security.ssl.BaseSSLSocketImpl.shutdownInput(BaseSSLSocketImpl.java:218)
        at sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:643)
        at sun.security.ssl.SSLSocketImpl.bruteForceCloseInput(SSLSocketImpl.java:598)
        at sun.security.ssl.SSLSocketImpl.duplexCloseOutput(SSLSocketImpl.java:558)
        at sun.security.ssl.SSLSocketImpl.close(SSLSocketImpl.java:471)
        at sun.security.ssl.SSLSocketImpl$AppOutputStream.close(SSLSocketImpl.java:997)
        at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
        at org.postgresql.core.PGStream.close(PGStream.java:694)
        at org.postgresql.core.QueryExecutorBase.close(QueryExecutorBase.java:155)
        at org.postgresql.jdbc.PgConnection.close(PgConnection.java:743)
        at xxxxx.db.impl.Connecter.closeAll(Connecter.java:263)
        at xxxxx.db.impl.Connecter.reset(Connecter.java:288)
[...] 
        at java.lang.Thread.run(Thread.java:748)}

)

Is this indicative of a problem? Should the JDBC driver code be catching this exception or should we? Thanks!

Issue Analytics

State:
Created 2 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

davecramercommented, Nov 17, 2021

Apologies. And it turns out we don’t check to see if it is closed already. I’ll sort this out today. Thanks

1reaction

davecramercommented, Nov 16, 2021

Closing due to lack of activity. Please reopen if you have more information

Top Results From Across the Web

SSLSocket duplex close failed - java - Stack Overflow

I experienced this behavior with openJDK11 and above, it seems due to the new implementation of SSL/TLS channel in Java 11 in order...

SSLSocket duplex close failed messages in logs after ...

Cause: JDK 8u261 introduced a new format for TLS logging. Additional data is now captured per event and logged. Exceptions handled by the...

Confusing log output: SSLSocket duplex close failed

end users complaining about the messaging of some new logger output seen with the new TLSv1.3 JDK library. in particular this example:

JDK-8207009 TLS 1.3 half-close and synchronization issues

JDK-8208642 - Server initiated TLSv1.2 renegotiation fails if Java client allows ... And the SSLSocket.close() specification also requires duplex-close.

ssl connection| JBoss.org Content Archive (Read Only)

javax.net.ssl|WARNING|03|Finalizer|2019-01-03 05:20:30.780 PST|SSLSocketImpl.java:494|SSLSocket duplex close failed (. "throwable" : {.