tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Woonsan Ko <>
Subject JNDI DataSource in Tomcat 8: maxTotal and maxWaitMillis
Date Tue, 24 May 2016 22:23:44 GMT

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
Browsing the source, o.a.t.jdbc.pool.PoolConfiguration doesn't seem to
consider both. o.a.t.jdbc.pool.DataSourceFactory#parsePoolProperties(Properties)
seems even unaware of those new properties.
Would this be a bug in either code or documentation?

Another question is, why does it ignore 'poolPreparedStatements'
parameter even though it's supported by the underlying dbcp?




To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message