Re: tomcat connection pool per database (postgres)

For those scoring at home, I'm going to try managing pool-per-user myself for the potential jmx gain and as I said, two will be amazing success. On 11/25/20 9:40 AM, Christopher Schultz wrote: Phil and Rob, On 11/24/20 11:26, Phil Steitz wrote: On 11/24/20 8:52 AM, Rob Sargent wrote: Perhap

Re: tomcat connection pool per database (postgres)

Phil and Rob, On 11/24/20 11:26, Phil Steitz wrote: On 11/24/20 8:52 AM, Rob Sargent wrote: Perhaps I read too much into the description of "The tomcat JDBC Connection Pool" page? TheJDBC Connection Pool|org.apache.tomcat.jdbc.pool|is a replacement or an alternative to theApache Commons DBCP

Re: tomcat connection pool per database (postgres)

On 24/11/2020 16:26, Phil Steitz wrote: > > > On 11/24/20 8:52 AM, Rob Sargent wrote: >> Perhaps I read too much into the description of "The tomcat JDBC >> Connection Pool" page? >> >> TheJDBC Connection Pool|org.apache.tomcat.jdbc.pool|is a replacement >> or an alternative to theApache Commons

Re: tomcat connection pool per database (postgres)

On 11/24/20 8:52 AM, Rob Sargent wrote: Perhaps I read too much into the description of "The tomcat JDBC Connection Pool" page? TheJDBC Connection Pool|org.apache.tomcat.jdbc.pool|is a replacement or an alternative to theApache Commons DBCP connection pool

Re: tomcat connection pool per database (postgres)

Perhaps I read too much into the description of "The tomcat JDBC Connection Pool" page? TheJDBC Connection Pool|org.apache.tomcat.jdbc.pool|is a replacement or an alternative to theApache Commons DBCP connection pool. I reacted to the "replacement" bit. Are

Re: tomcat connection pool per database (postgres)

On 11/24/20 8:14 AM, Rob Sargent wrote: Thanks. I get it. But... - seems this solution raises the footprint of the pooler, with number-of-users * minimum-connection-count etc - would it be beyond the pale for the pooler to maintain username-connectionList maps? Per response elsethread, se

Re: tomcat connection pool per database (postgres)

Thanks.  I get it. But... - seems this solution raises the footprint of the pooler, with number-of-users * minimum-connection-count etc - would it be beyond the pale for the pooler to maintain username-connectionList maps? Thankfully, I'll be wildly successful if I have two concurrent users

Re: tomcat connection pool per database (postgres)

Rob, On 11/19/20 12:38, Rob Sargent wrote: Since the connection URL names a specific postgres database is it standard practice to have a pool per target database?  (Switching databases in postgres amounts to closing/opening a connection.) I generally consider a database connection pool to be