Re: JNDI DataSource in Tomcat 8: maxTotal and maxWaitMillis

2016-05-25 Thread Woonsan Ko
Hi Mark, On Wed, May 25, 2016 at 4:56 AM, Mark Thomas wrote: > On 24/05/2016 23:23, Woonsan Ko wrote: >> Hi, >> >> Since 8.0, I think we should use maxTotal instead of maxActive and >> maxWaitMillis instead of maxWait. [1,2] >> However, if I use maxTotal for instance, the jmx console doesn't show

Re: JNDI DataSource in Tomcat 8: maxTotal and maxWaitMillis

2016-05-25 Thread Mark Thomas
On 24/05/2016 23:23, Woonsan Ko wrote: > Hi, > > Since 8.0, I think we should use maxTotal instead of maxActive and > maxWaitMillis instead of maxWait. [1,2] > However, if I use maxTotal for instance, the jmx console doesn't show > it but show the old maxActive value (100, probably the default > v

JNDI DataSource in Tomcat 8: maxTotal and maxWaitMillis

2016-05-24 Thread Woonsan Ko
Hi, Since 8.0, I think we should use maxTotal instead of maxActive and maxWaitMillis instead of maxWait. [1,2] However, if I use maxTotal for instance, the jmx console doesn't show it but show the old maxActive value (100, probably the default value?). Browsing the source, o.a.t.jdbc.pool.PoolConf