Bug 64083

Summary: JDBC pool keeps closed connection as available
Product: Tomcat Modules Reporter: Alex Panchenko <alex.panchenko>
Component: jdbc-poolAssignee: Tomcat Developers Mailing List <dev>
Status: NEW ---    
Severity: normal CC: alex.panchenko
Priority: P2    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Alex Panchenko 2020-01-17 16:53:01 UTC
In my case the PG driver has closed connecction because of kind of I/O error - an attempt to pass too many parameters for PreparedStatement.

I've created an example: https://github.com/panchenko/tomcat-bugs/blob/master/jdbc-return-closed-connection/src/test/java/org/example/jdbc/ReturnClosedConnectionTest.java

However that closed connection was added to the avaiable ones in the ppol (despite an error during clearWarnings, etc).

And then some other code got that closed connection and failed.

The pool request: https://github.com/apache/tomcat/pull/235