You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jeremy Bauer (JIRA)" <ji...@apache.org> on 2011/02/02 05:14:30 UTC
[jira] Created: (OPENJPA-1935) Informix lock exceptions are not
mapped properly by OpenJPA
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
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
[jira] Commented: (OPENJPA-1935) Informix lock exceptions are not
mapped properly by OpenJPA
Posted by "Jeremy Bauer (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (OPENJPA-1935) Informix lock exceptions are not
mapped properly by OpenJPA
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (OPENJPA-1935) Informix lock exceptions are not
mapped properly by OpenJPA
Posted by "Jeremy Bauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer resolved OPENJPA-1935.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
2.1.0
> 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
> Fix For: 2.1.0, 2.2.0
>
>
> 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
[jira] [Closed] (OPENJPA-1935) Informix lock exceptions are not
mapped properly by OpenJPA
Posted by "Albert Lee (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-1935.
-------------------------------
Close issue in preparation for 2.2.0 release.
> 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
> Fix For: 2.1.0, 2.2.0
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira