Bug 1151071
Summary: | When expose-all-logs is not set for JTS no transaction is shown in jboss-cli | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ondrej Chaloupka <ochaloup> | ||||
Component: | Transaction Manager | Assignee: | Michael <mmusgrov> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Hayk Hovsepyan <hhovsepy> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.4.0 | CC: | hhovsepy, kkhan, rsvoboda, tom.jenkinson | ||||
Target Milestone: | DR11 | Keywords: | Regression | ||||
Target Release: | EAP 6.4.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-08-19 12:41:04 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1165728 | ||||||
Attachments: |
|
Description
Ondrej Chaloupka
2014-10-09 14:27:49 UTC
Created attachment 945351 [details]
tx-object-store.zip
I was thinking that setting the property to true by default is not so good. If I have structure like this: $JBOSS_HOME/standalone/data/tx-object-store/ ├── ShadowNoFileLockStore └── defaultStore ├── CosTransactions │ └── XAResourceRecord │ └── 0_ffff0a280545_2d64af2f_54378290_3c ├── Recovery │ └── FactoryContact │ ├── 0_ffff0a280545_2d64af2f_54378290_12 │ └── 0_ffff0a280545_e75f515_543782b1_16 └── RecoveryCoordinator └── 0_ffff52e38d0c_c91_4140398c_0 then operation on reading resources from log-store (/subsytem=transactions/log-store=log-store:read-resource()) will show 4 "transactions" and it's just on you to understand what is real transaction and what is record fro recovery coordinator. By default it should show just "real" transaction in store and when you know what you are doing then expose-all-logs could be used. As it is currently there is information about no transaction shown without expose-all-logs. As mentioned - it worked for 6.3.0.GA where the result was following: { "outcome" => "success", "result" => { "type" => "default", "transactions" => {"0:ffff0a280545:-477f44a9:5436a3c5:46" => { "age-in-seconds" => "679213", "id" => "0:ffff0a280545:-477f44a9:5436a3c5:46", "jmx-name" => undefined, "type" => "StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple", "participants" => {"1" => { "eis-product-name" => undefined, "eis-product-version" => undefined, "jmx-name" => undefined, "jndi-name" => "1", "status" => "PREPARED", "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord" }} }} } } As this is regression against behaviour of 6.3.0.GA setting blocker to ? for not being forgotten as should be part of 6.4.0.GA. Verified on revision EAP 6.4.0.DR11 |