add JPA 2.0 locking

Description

Move it to 3.5 if you won't have it done for Beta3...

Attachments

4

is a fix for

is followed up by

Activity

Steve EbersoleMarch 21, 2011 at 7:09 PM

Bulk closing stale resolved issues

Scott MarlowJanuary 8, 2010 at 1:25 AM

lock support is in place. We will open a separate jira for updating the Dialects to fully (as best as possible) support locking.

Steve EbersoleJanuary 8, 2010 at 12:18 AM

Move it to 3.5 if you won't have it done for Beta3...

Emmanuel BernardDecember 10, 2009 at 11:59 AM

Actually, LockTimeoutException is not limited to javax.persistence.lock.timeout

"When the lock cannot be obtained, and the database locking failure results in only statement-level roll- back, the provider must throw the LockTimeoutException (and must not mark the transaction for rollback)." section-3.4.4.2

Emmanuel BernardDecember 10, 2009 at 10:55 AM

Scott,
When you are done implementing javax.persistence.lock.timeout and map it to an Hibernate LockTimeoutException,
Make sure to edit AbstractEntityManagerImpl#convert and add the mapping between the Hibernate Exception and JPA's javax.persistence.LockTimeoutException

I've added the logic to not rollback the transaction when javax.persistence.LockTimeoutException is raised.

Also, the persistence context must be in a usable state after a lock timeout exception (unlike many exceptions we raise).

Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created November 4, 2009 at 6:06 PM
Updated March 21, 2011 at 7:09 PM
Resolved January 8, 2010 at 1:25 AM