Bug 1086297 - JBoss CLI does not know to work with CMR data from object store log
Summary: JBoss CLI does not know to work with CMR data from object store log
Keywords:
Status: CLOSED DUPLICATE of bug 1113225
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Michael
QA Contact: Ondrej Chaloupka
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-10 14:56 UTC by Ondrej Chaloupka
Modified: 2014-10-25 12:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-08 13:34:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
tx-object-store dir (4.53 KB, application/zip)
2014-04-10 14:56 UTC, Ondrej Chaloupka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1113225 0 unspecified CLOSED CMR: TX log does not show participants after crash. 2021-02-22 00:41:40 UTC

Internal Links: 1113225

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 ***


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