[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6865?page=c...
]
Gail Badner commented on HHH-6865:
----------------------------------
IIRC, pre-4.0 Hibernate did not immediately convert SQLException to JDBCException when the
statement failed, instead that conversion happened in the locking strategy classes.
PessimisticLockException should be thrown when pessimistic read and
write locking strategies fail
-------------------------------------------------------------------------------------------------
Key: HHH-6865
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6865
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 4.0.0.CR6
Reporter: Gail Badner
Assignee: Gail Badner
Fix For: 4.0.0.next
In some cases, when a pessimistic read/write locking strategy fails with SQLException,
Hibernate converts the SQLException to a org.hibernate.JDBCException, but does not wrap
the JDBCException in a org.hibernate.PessimisticLockException.
This affects:
PessimisticReadSelectLockingStrategy.lock(...)
PessimisticReadUpdateLockingStrategy.lock(...)
PessimisticWriteSelectLockingStrategy.lock(...)
PessimisticWriteUpdateLockingStrategy.lock(...)
These methods specifically catch SQLException, convert it to a
org.hibernate.JDBCException, and wrap in a org.hibernate.PessimisticLockException.
If Hibernate does the conversion immediately when the statement fails and throws
JDBCException, then lock(...) does not have the opportunity to catch it and wrap it in a
org.hibernate.PessimisticLockException.
This issue is reproduced in LockTest failures on Oracle.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira