Has something changed on TC 8 requiring some different configuration for
SQL connections? I just installed 8.0.15 on three servers (see last
week's post regarding errors on 8.0.17). All three servers work for a
while. Then after about an hour I start getting the following errors:
java.sql.SQLException: Cannot get a connection, general error
at
org.apache.tomcat.dbcp.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:130)
at
org.apache.tomcat.dbcp.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1412)
I bounce Tomcat, and it works again for another hour or so. Then it
hits again.
None of the servers are high-traffic. I can pretty much guarantee I'm
not truly using up all connections.
This is failing identically on all three servers (unrelated customers
and unrelated apps... just migrated all my servers at the same time).
I moved back to Tomcat 7, no change otherwise to config, etc. The
problem went away on all servers. So it's definitely related to TC 8.
Please help. I want to move up to TC 8. Do I need to make some
mandatory config changes to something to make TC 8 happy with regard to
SQL connections? Or do I have some catastrophic bug in my code with
regard to connections that TC7 was letting slide and TC8 is now
enforcing? If so, is there a way to monitor TC's connection pool stats
and figure this out?
Thanks.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
