Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

2015-10-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bradley, On 10/7/15 4:04 PM, Bradley Wagner wrote: >> The general recommendation is to use the default pool >> (commons-dbcp). > > Great. Thanks! > >> Unless you have narrowed a performance problem to the pool >> itself, > there's no reason to

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

2015-10-07 Thread Bradley Wagner
> The general recommendation is to use the default pool (commons-dbcp). Great. Thanks! > Unless you have narrowed a performance problem to the pool itself, there's no reason to use one over the other. I suspect that there are only a few companies in the world where the connection pool

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

2015-10-07 Thread Bradley Wagner
Ah, I see what you're saying. My apologies for not seeing that sooner. That post was also very helpful in explaining why both exist. Thank you! Is it your recommendation then to use DBCP 2 over Tomcat JDBC in Tomcat 8? If so, I think it would be helpful to have a page on the public Tomcat

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

2015-10-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bradley, On 10/7/15 3:21 PM, Bradley Wagner wrote: > Ah, I see what you're saying. My apologies for not seeing that > sooner. > > That post was also very helpful in explaining why both exist. > Thank you! It's definitely confusing to those you