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

Mark Little (JIRA) issues at jboss.org
Wed Sep 24 11:43:02 EDT 2014

    [ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005779#comment-13005779 ] 

Mark Little commented on JBTM-2259:

OK, but this is not compliant with the standards and therefore if some other transaction engine is used it will break. The reason ordering of resources and synchronisations isn't supported in the standards is because it becomes very hard to manage global ordering in a heterogenous environment. Are we really happy to add something which basically ties IronJacamar and Narayana together? I'm no so sure. While it's nice to add something like resource ordering, as we do with AbstractRecords, it should be done cautiously, in situations where no other option is possible, or as an optimisation, i.e., so without it the system still works, but may be slower, less efficient etc.

> 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

More information about the jbossts-issues mailing list