Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Thu, 28 Mar 2013 15:31:15 +0000 (UTC)
From: "Pinaki Poddar (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: <JIRA.12429621.1246895454580.70184.1364484675786@arcas>
In-Reply-To: <JIRA.12429621.1246895454580@arcas>
References: <JIRA.12429621.1246895454580@arcas>
Subject: [jira] [Updated] (OPENJPA-1160) Failed transactions must generate
 more focussed (and accurate) message for the cause
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pinaki Poddar updated OPENJPA-1160:
-----------------------------------

    Fix Version/s: 2.0.0
    
> 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
>             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