On 22/02/2023 04:58, Konstantin Kolinko wrote:
ср, 22 февр. 2023 г. в 01:31, Artur Tomusiak - Hannon Hill
<artur.tomus...@hannonhill.com>:
After upgrading from Tomcat 9.0.33 to Tomcat 9.0.69,
Note that using a binary search (bisection) one could limit the version range.
Relevant version information is:
9.0.71 - DBCP f131286 2.10.0-SNAPSHOT 2022-12-30
9.0.53 - DBCP 2abdb49 2.9.0 2021-08-03
9.0.42 - DBCP e24196a 2.9.0-SNAPSHOT 2021-01-15
9.0.38 - DBCP 6d232e5 2.8.0-SNAPSHOT 2020-08-11
9.0.30 - DBCP a363906 2.8.0-SNAPSHOT 2019-12-06
Alternatively, it is possible to reconfigure the pool to use Apache
Commons DBCP 2 and Apache Commons Pool 2 directly (instead of
package-renamed version used by Tomcat), and bisect their version
ranges.
Given Tomcat's tendency to update to specific commits rather than
releases, bisecting Tomcat versions is probably easier.
Does your database provide any form of debug logging? The additional
commands should be easy to spot in such a log.
Changes to autoCommit and readOnly handling in 9.0.38 could result in
additional database calls. See
https://issues.apache.org/jira/browse/DBCP-558
I don't see anything else obvious in the change history but a debug log
for the connection is likely to be the quickest way to see what is going on.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org