Bug 1001909 - Last resources is not committed prior to other resources
Summary: Last resources is not committed prior to other resources
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: DR12
: EAP 6.4.0
Assignee: tom.jenkinson
QA Contact: Hayk Hovsepyan
Depends On:
Blocks: 1002330 1002584
TreeView+ depends on / blocked
Reported: 2013-08-28 05:46 UTC by James Livingston
Modified: 2019-08-19 12:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1002330 (view as bug list)
Last Closed:
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBTM-1431 0 Major Closed LastResourceRecord.shouldAdd allows insertion regardless of order and type info 2017-03-21 05:43:37 UTC

Description James Livingston 2013-08-28 05:46:34 UTC
Due to https://issues.jboss.org/browse/JBTM-1431, it is possible for a last resource (e.g. non-XA resource) to be committed prior to another XA resource, which is unsafe.

This was fixed in master prior to 6.1, but not in a bugfix release so was not pulled into EAP.

Comment 1 James Livingston 2013-08-28 22:36:19 UTC
Fix backported to 4.17 branch by Tom, https://github.com/jbosstm/narayana/commit/986d7792d2dbcc5d01844a5f2240a31a1f5d78b2

Comment 2 JBoss JIRA Server 2013-10-14 11:55:47 UTC
Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-1431 to Closed

Comment 5 tom.jenkinson 2014-12-05 12:42:36 UTC
Went into 4.17.9

Comment 6 Hayk Hovsepyan 2014-12-08 14:29:46 UTC
Verified on revision EAP 6.4.0.DR12.
Last resource is committed before XA resources.

For safety reasons the "Commit Markable Resource" is added in EAP 6.3.0. (http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#sect-About_the_LRCO_Optimization_for_Single-phase_Commit_1PC)

Note You need to log in before you can comment on or make changes to this bug.