Issue Details (XML | Word | Printable)

Key: OPENJPA-102
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Patrick Linskey
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OpenJPA

JTA transaction rollback, nonexistant instances, transactional persistence context => failures during afterCompletion() and close()

Created: 17/Jan/07 04:07 AM   Updated: 01/Mar/07 02:13 AM
Return to search
Component/s: jpa, kernel
Affects Version/s: None
Fix Version/s: 0.9.7

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works openjpa-detach.patch 2007-01-17 04:09 AM Patrick Linskey 2 kB
Environment: WebLogic Server 10.0

Resolution Date: 17/Jan/07 10:17 PM


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order