Bump com.mchange:c3p0 from 0.10.1 to 0.11.1

[dependabot]

Bumps com.mchange:c3p0 from 0.10.1 to 0.11.1.

Changelog

Sourced from com.mchange:c3p0's changelog.

c3p0-0.11.1 -- in BasicResourcePool, forceKillAcquires() accidentally failed to surrender its lock, leading to deadlocks following a full round of acquisition failures. Many thanks to @​pwielgolaski on github for tracking down the issue, to @​driseley on github for providing a reproduction of the issue, and to @​michalgutkowski on github for providing a pull request with the fix. c3p0-0.11.0 -- Additional testing. c3p0-0.11.0-pre2 -- Define new property cancelAutomaticallyClosedStatements, which, if true, ensures that Statement.cancel() will be called prior to Statement.close() when c3p0 automatically close()es statements because a client has neglected to, a Connection with open Statements has exceeded its unreturnedConnectionTimeout, or the Statement cache is expiring a PreparedStatement. Thanks to Andreas Dangel (in 2014!) for pointing out scenarios where this might be helpful, and offering a PR demonstrating the basic fix, and Luis Paolini for reminding me that I flaked 11 years ago and this is still worth pursuing. c3p0-0.11.0-pre1 -- Rewrite BasicResourcePool and GooGooStatementCache in terms of ReentrantLock and Condition.{await/signalAll} rather than native monitors and wait()/notifyAll(), because wait() pins loom virtual threads. Many thanks to alex-kormukhin for calling attention to this issue and proposing the fix! -- Double check after termination of BasicResourcePool.awaitAvailable(...) that following notification/termination a resource (Connection) remains available. Many thanks to C3Stones and xtb359 on github for calling attention to this issue. -- Prevent fragility under non-bootstrap / non-system CLASSLOADERs under Java 8, where references to java.sql.ShardingKey not available under Java 8 provoke NoClassDefFoundError. Bifurcate Connection proxies, generate version without sharding key methods under JVMs where ShardingKey is unavailable, full JDBC 4.3 Connection API proxies where ShardingKey is present. Thanks to Force Rs on github for finding the issue and suggesting the solution! c3p0-0.10.2 -- Prevent freeze due to re-waiting if a non-Exception Throwable occurs while acquiring a PreparedStatement to cache. Thanks Totyo Totev! 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.

... (truncated)

Commits

• 73e77ed Update CHANGELOG, build.mill publishVersion for 0.11.1 final. Add RELEASE_NOT...
• b1b2aa6 Add mill wrapper script, .mill-version file.
• 9ad6a36 Merge pull request #190 from michalgutkowski/patch-1
• bc24ad0 add missing unlock()
• 7d0e9f7 Bump version for 0.11.0 final.
• eddc46e Move older release notes into 'release-notes-past' directory.
• b6a82ec Define release notes for c3p0-0.11.0
• 1777d72 Tweak README.md.
• a876dfa Tweak README.md.
• ab3976b Cap CHANGELOG for, update version to, 0.11.0-pre2
• 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Test Results

96 tests   95 ✅  1m 24s ⏱️
39 suites   1 💤
39 files     0 ❌

Results for commit 87d413c.

♻️ This comment has been updated with latest results.

[dependabot]

Superseded by #393.