Bug 1086297

Summary: JBoss CLI does not know to work with CMR data from object store log
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Chaloupka <ochaloup>
Component: Transaction ManagerAssignee: Michael <mmusgrov>
Status: CLOSED DUPLICATE QA Contact: Ondrej Chaloupka <ochaloup>
Severity: urgent Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: hhovsepy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-08 13:34:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
tx-object-store dir none

Description Ondrej Chaloupka 2014-04-10 14:56:27 UTC 
Created attachment 884986 [details]
tx-object-store dir

It seems that the jboss cli tool does not know to work with log object store created by CMR recovery module.

If I observe correctly when server crashes in the middle of 2PC process and is started again then immediately after first recovery there is a change in the object store structure. Instead of "folder" AtomicAction the CMR transaction is moved to AtomicActionConnectable. 
It seems that jboss cli does not expect such thing and such transaction is not shown in the list of the unfinished transactions when log store is probed:
/subsystem=transactions/log-store=log-store:probe()
/subsystem=transactions/log-store=log-store:read-resource(recursive=true, include-runtime=true)

The transaction object store directory structure before probing is following (directory added as attachment):
standalone/data/tx-object-store/
└── ShadowNoFileLockStore
    └── defaultStore
        ├── EISNAME
        │   ├── 0_ffff7f000001_-77b4fce2_53468e5c_27
        │   └── 0_ffff7f000001_-77b4fce2_53468e5c_35
        └── StateManager
            └── BasicAction
                └── TwoPhaseCoordinator
                    ├── AtomicAction
                    └── AtomicActionConnectable
                        └── 0_ffff7f000001_-77b4fce2_53468e5c_4f
Comment 1 Ondrej Chaloupka 2014-07-08 13:34:08 UTC 

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