[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-7034) java.sql.SQLTimeoutException should be mapped to org.hibernate.QueryTimeoutException

[Gail Badner (JIRA)]

    [ https://hibernate.onjira.com/browse/HHH-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45403#comment-45403 ] 

Gail Badner commented on HHH-7034:
----------------------------------

An alternative is for Oracle10gDialect to override Dialect.buildSQLExceptionConversionDelegate) with a delegate that maps ORA-01013 to org.hibernate.QueryTimeoutException.

ORA-01013 usually indicates a timeout, but it can also have other causes:
http://www.dba-oracle.com/t_ora_01013_user_requested_cancel_of_current_operation.htm

> java.sql.SQLTimeoutException should be mapped to org.hibernate.QueryTimeoutException
> ------------------------------------------------------------------------------------
>
>                 Key: HHH-7034
>                 URL: https://hibernate.onjira.com/browse/HHH-7034
>             Project: Hibernate ORM
>          Issue Type: Bug
>          Components: core
>            Reporter: Gail Badner
>            Assignee: Gail Badner
>             Fix For: 4.1.0
>
>
> In SQLExceptionTypeDelegate.convert(), java.sql.SQLTimeoutException should be mapped to org.hibernate.QueryTimeoutException.
> This fixes the org.hibernate.ejb.test.lock.LockTest failures on oracle11gR2:
> - testQueryTimeout()
> - testQueryTimeoutEMProps()
> I did not test this on oracle11gR2RAC, but the failures appear to be the same as oracle11gR2.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira