DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-985
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 1
Operations

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

When calling ExecutionContext.close on JTA transaction only check the "active" flag (i.e don't trigger rejoin)

Created: 20/Jan/13 12:12 PM   Updated: 04/Feb/13 07:13 PM   Resolved: 27/Jan/13 05:14 PM
Component/s: Transactions
Affects Version/s: None
Fix Version/s: 3.2.0.m3


Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson made changes - 20/Jan/13 12:12 PM
Field Original Value New Value
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 21/Jan/13 07:51 PM
Status Resolved [ 5 ] Closed [ 6 ]
Andy Jefferson made changes - 27/Jan/13 05:14 PM
Resolution Fixed [ 1 ]
Status Closed [ 6 ] Reopened [ 4 ]
Andy Jefferson made changes - 27/Jan/13 05:14 PM
Status Reopened [ 4 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 27/Jan/13 07:51 PM
Comment [ Maybe JBoss require this TransactionSynchronizationRegistry.registerInterposedSynchronization(...) calling instead? but then why does JTA have two mechanisms for the same apparent thing, and would it work registering on both, or just one, or what? That question is general to JTA across all JTA implementations, what would work for all? ]
Andy Jefferson made changes - 01/Feb/13 07:41 AM
Status Resolved [ 5 ] Closed [ 6 ]