[
https://issues.apache.org/jira/browse/OPENJPA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989836#comment-12989836
]
Jeremy Bauer commented on OPENJPA-1935:
---------------------------------------
Thanks, Pinaki. I have a fix brewing down the DBDictionary.narrow path. It
actually overwrites matchErrorState (called by narrow to determine the
exception type) and fixes isFatalException which is also semi-broken in the
Informix dictionary. I just need to finish cleaning up the jUnits before
posting a fix... :-)
> Informix lock exceptions are not mapped properly by OpenJPA
> -----------------------------------------------------------
>
> Key: OPENJPA-1935
> URL: https://issues.apache.org/jira/browse/OPENJPA-1935
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.1.0, 2.2.0
> Environment: Informix IDS 10 and IDS 11
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Labels: Informix, exception, lock
>
> Locking type failures are not mapped correctly when using Informix with
> OpenJPA. When a SQLException with generic sql state value 'IX000' is
> returned, it gets mapped to a query exception. Instead, the underlying
> SQLException(s) should be inspected for specific lock or lock timeout sql
> codes to determine the correct exception type.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
