On 3/24/2018 5:04 PM, Mark Thomas wrote:
There are two pools available.
<snip>
org.apache.tomcat.jdbc.pool.DataSourceFactory is a different pool developed in the Tomcat project (generally called JDBC pool).
OK, so that means that the currently active config is using dbcp. The *new* config that I'm building is using the tomcat pool, with the factory specified in the Tomcat JDBC pool documentation. I do have at least one of the tomcat-specific configuration options in that config I'm building. See the initial message on the thread for examples of both configurations.
Which directs me back to the second question I asked in the initial message: Why does the application on the staging server appear to open a HUGE number of connections on startup when configured with the tomcat pool (which overloads the server and makes startup fail), and doesn't do that when configured with dbcp? The number of connections that I am told were opened (I wasn't involved with the restart and can't confirm what they said) is far more than should have been possible. The configs are fairly similar, but I have a lot more options on the new config, designed to try and keep the connection count down.
I should figure out which version of the MySQL driver we have. I know for sure that there have been bugs in older releases and I have had trouble when not using the latest.
Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
