[
https://issues.apache.org/jira/browse/OPENJPA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465546
]
Patrick Linskey commented on OPENJPA-102:
-----------------------------------------
New approach: I am going to change OpenJPA's detach algorithms to handle
failures more gracefully, and back out the patch I mentioned earlier. This will
resolve the unexpected exceptions I was seeing.
Separately, OPENJPA-104 tracks the JPA spec discrepancy.
> JTA transaction rollback, nonexistant instances, transactional persistence
> context => failures during afterCompletion() and close()
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-102
> URL: https://issues.apache.org/jira/browse/OPENJPA-102
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa, kernel
> Environment: WebLogic Server 10.0
> Reporter: Patrick Linskey
> Attachments: openjpa-detach.patch
>
>
> Configuration:
> - transactional persistence context
> - DetachState=fgs
> - JTA transactions
> If an error causes the transaction manager to roll back the current
> transaction, BrokerImpl.afterCompletion() will be invoked with
> Status.STATUS_ROLLEDBACK. afterCompletion() will call BrokerImpl.free(),
> which will attempt to load the default fetch group. If there is an instance
> in the Broker's context that does not exist (that was looked up via
> EntityManager.getReference(), for example), then the code in free() will fail
> with an ObjectNotFoundException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
