You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Alex Radivanovich (JIRA)" <ji...@apache.org> on 2009/12/11 20:46:18 UTC

[jira] Commented: (OPENJPA-1048) Dirty check fails with ConcurrentModificationException during rollback

    [ https://issues.apache.org/jira/browse/OPENJPA-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789488#action_12789488 ] 

Alex Radivanovich commented on OPENJPA-1048:
--------------------------------------------

The exception seems to appear when entity classes are not enhanced.
In my case ConcurrentModificationException has gone when I configured OpenJPA agent as described in http://openjpa.apache.org/builds/1.2.1/apache-openjpa-1.2.1/docs/manual/ref_guide_pc_enhance.html#ref_guide_pc_enhance_runtime

> Dirty check fails with ConcurrentModificationException during rollback
> ----------------------------------------------------------------------
>
>                 Key: OPENJPA-1048
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1048
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>
> Rollback caused by application failure breaks the code as reported in [1].
> It is to be ascertained whether this failure is caused only in runtime enhancement.
> In either case, the exception handling must be improved than:
> Caused by: <openjpa-2.0.0-SNAPSHOT-r422266:765846M nonfatal general error> org.apache.openjpa.persistence.PersistenceException: null
>         at org.apache.openjpa.kernel.BrokerImpl.afterCompletion(BrokerImpl.java:1973)
>         at 
> [1] http://n2.nabble.com/ConcurrentModificationException-tc2661811.html

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