Title: About the LRCO Optimization for Single-phase Commit (1PC) In Section 10.3.2 it describes only old LRCO Optimization mechanism. But it needs new section about Commit Markable Resource (new implementation of LRCO algorithm) algorithm description as well. Original bug from which it is cloned is about adding new section about the same new CMR algorithm in Administration and Configuration Guide. +++ This bug was initially created as a clone of Bug #1073834 +++ Hi, in EAP 6.3.0 transaction team implemented new feature as documented here: https://issues.jboss.org/browse/PRODMGT-49 It's new implementation of LRCO algorithm which makes non-xa resource fully recoverable (if it's database datasource and as it's just one in the XA transaction). It's necessary to document this new feature. Good person to contact is Tom Jenkinson <tom.jenkinson>. Please, then document that this new datasource needs to have new argument "connectable" set to true. It would be probably fine to add this thing under the section about configuraton of XA and non-XA datasources (like http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#Configure_an_XA_Datasource) Thank you Ondra
Reassigned to Nidhi Chaudhary as Lucas is committed to other work at present.
Added topic #30533 to Development Guide. Changes will be visible in the next build.
Changes are visible here: 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
*** Bug 1073834 has been marked as a duplicate of this bug. ***
The section on adding a CMR should mention that the setting will not take affect until the server is restarted - thanks.
Checked in revision: 6.3.0-11. Comment https://bugzilla.redhat.com/show_bug.cgi?id=1086849#c12 made by Tom was added after putting ON_QA, so they are not available. But still the info in this comment is important to be mentioned in documentation, so reopening the bug.
Sande, thanks for reviewing the topic. :)
Added the note about restarting the server. Changes will be visible in the next build.
Verified on EAP-6.3.0.ER3-rebuild1