[
https://issues.apache.org/jira/browse/OPENJPA-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar resolved OPENJPA-1160.
------------------------------------
Resolution: Fixed
Assignee: Pinaki Poddar
> Failed transactions must generate more focussed (and accurate) message for
> the cause
> ------------------------------------------------------------------------------------
>
> Key: OPENJPA-1160
> URL: https://issues.apache.org/jira/browse/OPENJPA-1160
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.0.0
>
>
> OptimisticException is overused as a generic cause of many kinds of failure
> during a commit or flush (which at times are not directly related to a
> optimistic concurrency violation per se).
> Given that the error message is often the first handle to analyze a fault, we
> should
> a) analyze all places that raise OptimisticLockexception
> b) attempt to narrow the exception or at least provide a differentiated
> message for the cause to the user
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
