[OPENJPA-1565] QueryTimeOut and LockTimeOut exceptions are not raised correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M1, 2.0.0-M2, 2.0.0-M3, 2.0.0-beta, 2.0.0-beta2
• Fix Version/s: 2.0.0-beta3
• Component/s: jdbc, jpa, kernel, query, sql
• Assignee: Pinaki Poddar
• Reporter: Pinaki Poddar
• Created: 11/Mar/10 22:51
• Updated: 07/Apr/10 15:18
• Resolved: 22/Mar/10 20:11

Description

Narrowing SQL Exception to a more specific exception such as lock or query or referential integrity violation does not distinguish correctly whether a query or lock request has timed out.
This distinction is critical for JPA 2.0 spec compliance because QueryTimeOut and LockTimeOut exceptions are not supposed to cause rollback as per the spe (Section 3.9).

Issue Links

• is related to: OPENJPA-991 Implement LockTimeout using db specific server-side lock timeout feature
• relates to: OPENJPA-1594 Tests not handling new QueryTimeOut and LockTimeOut exceptions correctly
• relates to: OPENJPA-1609 PessimisticLockException instead of LockTimeoutException thrown on DB2V9 for ZOS
• relates to: OPENJPA-1614 Testcase failures in TextException on MSSQL

Sub-Tasks

• Tests not handling new QueryTimeOut and LockTimeOut exceptions correctly: Closed