openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (OPENJPA-634) SQLException not reported from Batched statement
Date Tue, 01 Jul 2008 16:22:45 GMT

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

Albert Lee reopened OPENJPA-634:
--------------------------------

      Assignee: Albert Lee

The previous fixes did not completely correct the problem scenario.

In AbstractUpdateManager.flush(), it keeps track of 2 exception collections, one as a local
variable in flush() and the 2nd one maintained by the prepare statement manger. These 2 collections
are combined into a single collection and returned by flush().

This approach caused the return collection not maintaining the order of exceptions took place
during the flush. Typically the first exception contains the relevant information about the
cause of failure and it allows the application to examine the cause and perform appropriate
recovery action.

Albert Lee.

> SQLException not reported from Batched statement
> ------------------------------------------------
>
>                 Key: OPENJPA-634
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-634
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.2.0
>            Reporter: Catalina Wei
>            Assignee: Albert Lee
>
> Batched update resulted in SQLException was not propagated back to application.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message