[
https://issues.apache.org/jira/browse/OPENJPA-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1048.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: The report is a 2.0.0-SNAPSHOT 'to
be ascertained' note that points to a dead nabble thread and has no reproducer,
so nobody can act on it. Please reopen if this still happens with OpenJPA 4.x.
> 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, UnenhancedClasses
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v10.3.26#10030026)
