[hibernate-issues] [JIRA] (HHH-16181) Leverage jakarta.persistence.lock.timeout for configuring tx/em-bound lock timeout

Michal Hajas ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzdhNmMxMWJh... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16181?atlOrigin=eyJpIjoiMzdhNm... ) HHH-16181 ( https://hibernate.atlassian.net/browse/HHH-16181?atlOrigin=eyJpIjoiMzdhNm... ) Leverage jakarta.persistence.lock.timeout for configuring tx/em-bound lock timeout ( https://hibernate.atlassian.net/browse/HHH-16181?atlOrigin=eyJpIjoiMzdhNm... ) Issue Type: Improvement Affects Versions: 6.1.6, 5.6.14 Assignee: Unassigned Components: hibernate-core Created: 14/Feb/2023 01:59 AM Environment: Hibernate 5.6.14/6.1.6 with Postgresql database Priority: Major Reporter: Michal Hajas ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Currently, when jakarta/javax.persistence.lock.timeout property is configured in the EMF config, the property does not work with Postgres because Postgres does not support the statement-level lock timeout hint. However, per discussion [1] , it seems possible to use this property to configure transaction or entity manager-bound lock timeout. [1] https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user/topi... ( https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user/topi... ) ( https://hibernate.atlassian.net/browse/HHH-16181#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16181#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#100216- sha1:7a51a57 )