Oh, I see that you already fetched the sources. Thank you! I'll be waiting for the next Tomcat release.
вт, 3 груд. 2024 р. о 15:24 robot carver <denixx.bay...@gmail.com> пише: > Mark, Rémy. > > A DBCP 2.13.0 was released. > > https://lists.apache.org/thread/ql22oo5xtr4jqp4g277vdzhodw8rxt9l > https://commons.apache.org/proper/commons-dbcp/download_dbcp.cgi > > Thanks! > Anton. > > чт, 21 лист. 2024 р. о 17:46 Mark Thomas <ma...@apache.org> пише: > >> On 21/11/2024 16:19, robot carver wrote: >> > чт, 21 лист. 2024 р. о 16:47 Rémy Maucherat <r...@apache.org> пише: >> > >> >> On Thu, Nov 21, 2024 at 4:33 PM robot carver <denixx.bay...@gmail.com> >> >> wrote: >> >>> >> >>> Hi! >> >>> I am posting this into the dev list as I am not familiar with the >> right >> >>> place for a DBCP issue in Tomcat's Bugzilla structure. >> >>> >> >>> I am seeking Rémy attention, as he is currently maintaining Tomcat 9. >> >>> >> >>> Could you please review this DBCP2 issue? >> >>> >> >>> I think Tomcat 9 has an issue with closing the abandoned connections >> (if >> >>> configured) since Tomcat 9.0.42: >> >>> "Update the internal fork of Apache Commons DBCP to 2.9.0 >> (2021-08-03). >> >>> Improvements, code clean-up and refactoring. (markt)" >> >>> >> >>> https://issues.apache.org/jira/browse/DBCP-599 >> >>> >> >>> The cool thing about this issue is that other Tomcat versions are also >> >>> affected, as I understand. >> >> >> >> 2.12.0 is the latest commons-dbcp release. >> > >> > Yep, the mentioned issue is true also for DBCP 2.12.0. >> > >> > I understand this issue is >> >> important to you, but reading it, it seems to need a very ancient DBCP >> >> driver to run into that. Maybe you should look into updating that >> >> first ? >> >> >> > I understand the statement about "you have a JDBC 4.0 driver and it is >> the >> > cause for this Error", >> > but what I try to convey: as I know, tomcat has no limits for the jdbc >> > version. >> > I meant there is no "must use JDBC 4.2 or more recent" requirement from >> > Tomcat side. >> > Also, a one-liner fix proposed by Gary Gregory repairs the issue with >> Error >> > thrown in a specific place, >> > where this issue is present, while keeping the absence of requirement >> for >> > JDBC 4.2, you could >> > use the JDBC 4.0 driver and be safe with your connection pool to be >> > maintained. >> >> And when Commons DBCP applies that fix and makes a release we will pick >> it up. >> >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >>
