Bump com.h2database:h2 from 2.4.240 to 2.5.250

[dependabot]

Bumps com.h2database:h2 from 2.4.240 to 2.5.250.

Release notes

Sourced from com.h2database:h2's releases.

version-2.5.250

Commits

• bba342d in preparation for a release
• 2763e82 in preparation for a release
• 7a267bc Merge pull request #4375 from excaliware/patch-1
• 297ff8e Merge pull request #4379 from jjh75607/fix/comment-on-view-column
• 46b0823 Reject COMMENT ON COLUMN for views and other tables that cannot be altered
• 9a8af38 Merge pull request #4363 from mayank1008-tech/Stop-server-everytime-db-instan...
• 3f68b6b Merge pull request #4374 from brettwooldridge/patch-1
• c436bf6 Merge pull request #4378 from momonari8/fix-getcostrangeindex-partial-sort-match
• 66a9786 MVStore: fix data race causing spurious "Position 0" during chunk rewriting
• 8d37836 Add regression test for the sort discount fix
• 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 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)

[mridulpathak]

Holding this for now: testIntegration surfaced a real, reproducible failure in service-dead-lock-retry-assert-data specifically on 2.5.250 (confirmed via a clean before/after baseline against 2.4.240), traced to a timing-fragile test from 2007 that only ever exercises H2, not MySQL/PostgreSQL. No CVEs are involved in this bump, so hardening that test's synchronization first, then will revisit merging this once trunk is stable with the fix in place.

[mridulpathak]

Holding off on this bump. While hardening testServiceDeadLockRetryThreadA/ThreadB (OFBiz-13585), we found H2 2.5.250 makes it fail deterministically (10/10), where 2.4.240 passed cleanly (0/20).

Root cause is a genuine H2 regression, not test flakiness: 2.5.250 dropped the rollback-path notification for transactions waiting on a rolled-back one, so waiters now always block for the full LOCK_TIMEOUT instead of resolving in milliseconds. That breaks bounded "rollback and retry" recovery like ServiceDispatcher.LOCK_RETRIES, since every retry loses H2's age-based deadlock tie-break to the still-unnotified original transaction.

Filed upstream: h2database/h2database#4391 (standalone repro, still present on H2 master).

No evidence of a real (non-test) OFBiz service pair with this exposure, and H2 is dev/test-only for production, so risk looks low — but holding until upstream responds rather than accepting silently.

[mridulpathak]

Update: H2 acknowledged the issue and merged a fix — h2database/h2database#4392 ("Restore notification of waiting transactions on a rollback"), merged to master 2026-09-14. Not yet in a tagged release though (latest tag is still 2.5.250, which doesn't include the fix). Holding this bump until a release containing the fix is available.