[jbossts-issues] [JBoss JIRA] (JBTM-2259) Allow the ordering of some synchronizations to be configurable

[Michael Musgrove (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2259:
-----------------------------------
    Fix Version/s: 6.0.0
                       (was: 5.0.4)


Moving out to 6 since there is a workaround:

"WildFly disables the delistResource calls in beforeCompletion, and IronJacamar kills the ManagedConnection if it detects a problem in afterCompletion."

We should push for ordering semantics in the next revision of the JTA spec:

There is a discussion in the comments to https://java.net/jira/browse/JTA_SPEC-4 and there are also some comments in JTA_SPEC-11

> 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: 6.0.0
>
>
> 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)