Bug 1073834 - Add new section about CommitMarkableResources - new implementation of LRCO argorithm for databases
Summary: Add new section about CommitMarkableResources - new implementation of LRCO a...
Keywords:
Status: CLOSED DUPLICATE of bug 1086849
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Russell Dickenson
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: eap63-beta-blockers 1086849
TreeView+ depends on / blocked
 
Reported: 2014-03-07 10:15 UTC by Ondrej Chaloupka
Modified: 2014-08-14 15:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1086849 (view as bug list)
Environment:
Build Name: 22508, Administration and Configuration Guide-6.3-1 Build Date: 06-03-2014 07:50:55 Topic ID: 4303-591659 [Latest]
Last Closed: 2014-04-28 03:16:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ondrej Chaloupka 2014-03-07 10:15:53 UTC
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

Comment 1 Ondrej Chaloupka 2014-04-11 10:08:49 UTC
The new properties of the transaction subsystem has to be documented. Please, add them to the table of possible configuration options.
The new element and properties are those which do the difference between jboss-as-txn_1_4.xsd and jboss-as-txn_1_5.xsd schema.

Comment 2 Ondrej Chaloupka 2014-04-23 10:11:12 UTC
Just mentioning planning jira for this new feature is here
https://issues.jboss.org/browse/EAP6-17

Comment 3 Nidhi 2014-04-28 03:16:54 UTC

*** This bug has been marked as a duplicate of bug 1086849 ***


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