[
https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-2259:
-------------------------------------
The case that is discussed on the forum is where two synchronizations both registered as
interposed need to have ordering imposed between them. The two Synchronizations are from
IronJacamar and a JPA persistence provider. When the JCA one runs, it closes the
underlying connection and so if it happens to have been registered first it will close the
connection before JPA flushes.
Allow the ordering of some synchronizations to be configurable
---------------------------------------------------------------
Key: JBTM-2259
URL:
https://issues.jboss.org/browse/JBTM-2259
Project: JBoss Transaction Manager
Issue Type: Enhancement
Components: JTA
Affects Versions: 5.0.3
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.0.4
IronJacamar delists resources in a beforeCompletion synchronization but under certain
circumstances (see attached forum thread) it may run before all JPA persistence providers
beforeCompletion synchronizations have been called (which breaks JPA).
The request is to add a configuration option to control the order in which certain
synchronizations are called.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)