[hibernate-issues] [JIRA] (HHH-16541) (Jakarta EE 10 Platform TCK) jpa/core/lock/query/Client.java\#getResultListTest1 test regression

Scott Marlow ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMThjNzYzYzk1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16541?atlOrigin=eyJpIjoiMThjNz... ) HHH-16541 ( https://hibernate.atlassian.net/browse/HHH-16541?atlOrigin=eyJpIjoiMThjNz... ) (Jakarta EE 10 Platform TCK) jpa/core/lock/query/Client.java\#getResultListTest1 test regression ( https://hibernate.atlassian.net/browse/HHH-16541?atlOrigin=eyJpIjoiMThjNz... ) Issue Type: Bug Affects Versions: 6.2.2 Assignee: Unassigned Created: 02/May/2023 06:35 AM Fix Versions: 6.2.3 Priority: Major Reporter: Scott Marlow ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The following Jakarta EE 10 Platform TCK tests are failing: jpa/core/lock/query/Client.java#getResultListTest1_from_appmanagedNoTx jpa/core/lock/query/Client.java#getResultListTest1_from_puservlet A clue is that the failure happens with git commit e96402a0052d320cbd0a82fe788b00b2d3fe81bf or newer (on Hibernate ORM 6.2 branch). The previous commit b754325cab919ccfe480ed126330105429004d58 passes the jpa/core/lock/query tests. The test output contains: ^[[0m^[[33m09:15:47,218 WARN [org.hibernate.sql.results.jdbc.internal.DeferredResultSetAccess] (default task-2) HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select (follow-on locking); results will be locked after initial query executes ^[[0m^[[33m09:15:47,250 WARN [org.hibernate.sql.results.jdbc.internal.DeferredResultSetAccess] (default task-2) HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select (follow-on locking); results will be locked after initial query executes ^[[0m[javatest.batch] ^[[0m^[[0m09:15:47,226 INFO [stdout] (Thread-197) 05-01-2023 09:15:47: SVR-ERROR: LockMoteType for the Employee[1] was wrong - Expected:PESSIMISTIC_READ, Actual:NONE [javatest.batch] ^[[0m^[[0m09:15:47,227 INFO [stdout] (Thread-197) 05-01-2023 09:15:47: SVR-ERROR: LockMoteType for the Employee[2] was wrong - Expected:PESSIMISTIC_READ, Actual:NONE The source is at https://github.com/jakartaee/platform-tck/blob/master/src/com/sun/ts/test... There are other (JPA) failures as well, will create separate jiras for others. Discussion started yesterday on this in https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/t... ( https://hibernate.atlassian.net/browse/HHH-16541#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16541#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100224- sha1:07bd2b7 )