I am suspecting that this confusion may even cause another severe error ( ). Currently 7.4 installation guide talks about only maxActive instead of maxTotal, and 8.3 guide does not state the importance of factory attribute - I have already seen a couple of customers misusing incorrect parameters. The guide should state above as a note because it is pretty important (if you misuse wrong parameters, for example misusing maxActive in Tomcat 8, then your setting will be ignored). Is my understanding above correct? If yes, here is my proposal to installation guide creation team: If you are using Tomcat 8, you should also add factory attribute as follows:įactory=".pool.DataSourceFactor".If you are using Tomcat 8, you should use maxTotal & maxWaitMillis.If you are using Tomcat 7, you can use maxActive & maxWait.In order to enable this new feature Tomcat JDBC Pool, you need to add factory attribute in your context.xml. For example, Tomcat JDBC Pool uses "maxTotal" instead of "maxActive" to limit the number of connections. Tomcat 7 and earlier version used Commons DBCP ("commons-dbcp"). Tomcat has updated its default connection pooling library to Tomcat JDBC Pool ("tomcat-jdbc-pool") in Tomcat 8.
There was a pretty big change made in Tomcat as to JDBC connection pool facility. Robotic Process Automation Design Patterns
0 kommentar(er)
