[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1278) It seems that LockAcquisitionException is never thrown out.

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278?page=all ]
     
Steve Ebersole closed HHH-1278:
-------------------------------

    Resolution: Fixed

Nope.  We actually ripped out all the code that used to interpret the vendor specific error codes because that stuff is a nightmare to maintain.  The core Hibernate code only ever uses the X/Open SQLState codes now to decipher the type of exception.  Unfortunately, there is not a standard X/Open SQLState code relating to lock acquisition errors.

If it is that important, just plugin in a custom SQLExceptionConverter and convert check your db vendor's specific lock acquisition issue error codes.

> It seems that LockAcquisitionException is never thrown out.
> -----------------------------------------------------------
>
>          Key: HHH-1278
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1
>  Environment: Win, Hibernate3.1, Oracle10G
>     Reporter: Dongsheng Wang

>
>
> I used to catch LockAcquisitionException to decide if I got the lock. It works.  After I update hibernate from 3.0 to 3.1. It seems that LockAcquisitionException is never thrown out. Instead, an JDBCException is thrown out. I checked the source, it seems that the LockAcquisitionException's constructor is never called by anybody. 
> Is it a bug or something?

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira