regression, we are no longer throwing PessimisticLockException as required by the JPA-2
spec
---------------------------------------------------------------------------------------------
Key: HHH-4850
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4850
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.0-Beta-3
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 3.5.0-Beta-4
It looks like the fix for HHH-4806 caused this to regress.
3.4.4.2
"
When an application locks an entity with LockModeType.PESSIMISTIC_READ and later updates
that entity, the lock must be converted to an exclusive lock when the entity is flushed to
the database[42].
If the lock conversion fails, and the database locking failure results in
transaction-level rollback, the
provider must throw the PessimisticLockException and ensure that the JTA transaction or
EntityTransaction has been marked for rollback. When the lock conversion fails, and the
database lock-
ing failure results in only statement-level rollback, the provider must throw the
LockTimeoutEx-
ception (and must not mark the transaction for rollback).
"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira