You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2011/02/02 22:39:28 UTC
[jira] Commented: (OPENJPA-1935) Informix lock exceptions are not
mapped properly by OpenJPA
[ https://issues.apache.org/jira/browse/OPENJPA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989811#comment-12989811 ]
Pinaki Poddar commented on OPENJPA-1935:
----------------------------------------
IX000 is specified as query error for Informix in sql-error-state-codes.xml. See DBDictionary.narrow(...) to overwrite for Informix.
> 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