aws-mysql-jdbc
aws-mysql-jdbc copied to clipboard
chore: Bump com.mchange:c3p0 from 0.9.5.5 to 0.10.1
Bumps com.mchange:c3p0 from 0.9.5.5 to 0.10.1.
Changelog
Sourced from com.mchange:c3p0's changelog.
c3p0-0.10.1 -- Implement more and "louder" (log ugly stack traces) validation of config properties. -- Modify former InUseLock (now InternalUseLock) and NewProxyConnection to use ReentrantLock rather than native monitors, to prevent pinning when clients run on loom virtual threads. Thanks Alex Kormukhin and Jeffrey Tucker! -- Implement config parameter markSessionBoundaries, so that users can disable JDBC 4.3 beginRequest / endRequest session boundary marking when JDBC drivers so undesirable things with those hints. Thanks Bikas Anand! -- Implement more careful examination of begin/endRequest methods, to take into account the case where those methods exist on the JDBC driver Connection implementation, but not in the Connection interface of a pre-Java-9 JVM. We still support begin/endRequest in this case, but reflectively. Thanks Vlad Skarzhevskyy, khushboo11-dotcom! c3p0-0.10.0 -- A bit more testing c3p0-0.10.0-pre7 -- Improve performance of begin/endRequest support -- Implement c3p0-loom UninstrumentedVirtualThreadPerTaskTaskRunnerFactory -- Change mind. Eliminate naggingly prescriptive equals/hashCode pseudorequirements from plugin interfaces, because our canonicalization strategy is by key, doesn' actually rely upon those implementations. -- Guard collection of MBeanAttributeInfo against items that would have no getter or setter to prevent ugly IntrospectionExceptions. See swaldman/c3p0#128 Thanks
@philippscs! -- Let C3P0PooledConnectionPool manager test introspected authentication that appears perhaps incomplete, and revert to NULL_AUTH (no-arg DataSource.getConnection()) if the test fails. See, should address, swaldman/c3p0#159 Thanks@sbaeumlisberger! c3p0-0.10.0-pre6 -- Lots of documentation work. -- Implement attemptResurrectOnCheckin config parameter. See swaldman/c3p0#47 Thanks Bartosz Radaczyński and Igor Khromov! -- Add guard to automaticTestTable preventing use of weird or potentially malicious table names. Thanks to Andy at Privitar -- Pick up com.mchange.v2.c3p0.impl.DefaultConnectionTester.isValidTimeout as default value of new connectionIsValidTimeout property, so that users upgrading from previous version still capture the setting from the old config, even as their ConnectionTester now falls back to null. c3p0-0.10.0-pre5 -- Lots of documenting, condensing, clean-up, etc. -- Define connectionIsValidTimeout as an ordinary bean-style config parameter. Previously users had to set a universal property (in c3p0.properties or System properties) to set this timeout. -- Use simplified isValid(...) based timeout by default, use traditional
... (truncated)
Commits
c666965Bump version for 0.10.1 final.3bc101fTweak release notes for c3p0-0.10.1c79baa1Write release notes, cap CHANGELOG, for c3p0-0.10.1.927efdbImplement more and louder validation of config properties.872613dComment duplicate setting in rough c3p0.properties, add some dev-notes.7fcd4e4Define abstract PercentXXFailConnectionTester, factor implementations into su...d2d6f0dAdd a couple of chaos testing resources.ca50283Fix misspelling in log message.dd89dd1Upgrade mchange-commons-java to v0.3.14a90a90Audit remaining uses of 'synchronized' within proxies.- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)