Hibernate 6.x Jakarta Data Pageable Migration Compatibility During Upgrade Recovery

Goal

Determine safe recovery procedures when upgrading from Hibernate 5.6 to 6.x pagination fails, specifically when Jakarta Data Pageable integration cannot be fully deployed due to runtime constraints.

Constraints

During upgrade transitions, Jakarta Data Pageable requires Java 17+ runtime, creating compatibility gaps for deployment environments that cannot immediately support the new dependency chain. ScrollableResults behavior changed significantly in 6.2+ with stricter cursor management, potentially causing resource leaks during partial upgrade states. Query.setFirstResult()/setMaxResults() now enforces stricter validation that may expose previously silent offset calculation errors.

Questions

Can Hibernate 6.x pagination be temporarily reverted to legacy setFirstResult()/setMaxResults() behavior while maintaining transaction consistency during failed upgrade recovery? What specific configuration properties or bootstrap settings enable this fallback without requiring full Jakarta Data Pageable dependency resolution?

How should ScrollableResults cursor management be reconfigured in 6.2+ to prevent resource leaks when recovery procedures force rollback to pre-upgrade connection handling patterns?