[ https://issues.jboss.org/browse/JBTM-1494?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1494: ------------------------------------- Agreed. Although, I think for certain applications you can mitigate the relaxed consistency by "moving the locks up to the application level". For example: A booking application commits the reservation to the DB in phase 0. The record shows that the booking is "pending". Other transactions see this and can decide what to do about a pending reservation (potentially over-booking, assuming some cancelations). in phase 2, the reservation is updated to either mark it as cancelled or complete (depending on the outcome of the transaction). Of course, this won't work for all applications, and when it does, it would impose a certain structuring on the application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira