I had a problem with similar symptoms a very long time ago. It turned out to be a bug in the version of mysql we were using. I substituted apache connection pool library and upgrade mysql version.
HTH Sent from my iPhone > On Oct 18, 2018, at 1:22 AM, Andrus Adamchik <and...@objectstyle.org> wrote: > > I am using Tomcat connection pool a lot, and I haven't seen this one. So > unfortunately no idea. Source code [1] only indicates that the error message > is indeed an interrupt of the wait for the connection. As to the source of > the interrupt, it is hard to say without checking the app. > > Andrus > > > [1] > https://apache.googlesource.com/tomcat/+/a9998cc0e9b48da47c0c656ef02ae37d7681d5eb/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#482 > >> On Oct 17, 2018, at 6:17 PM, t...@giaccone.org wrote: >> >> we've deployed an App to GKE and we're getting errors like: >> >> severity: "ERROR" >> textPayload: "java.sql.SQLException: Pool wait interrupted. >> at >> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:662) >> at >> org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:185) >> at >> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:127) >> >> the app has 16 connections configured in the JDBC driver. >> jdbc: >> db1: >> maxActive: 16 >> initialSize: 16 >> >> >> There's not much hitting this app, so I'm at a loss to understand why we're >> timing out. >> >> Any ideas what might be causing this? >> >> >> Tony Giaccone >
