-
1. Re: How transactions and participants resources are populated ?
tomjenkinson Aug 30, 2017 12:36 PM (in response to claudio4j)You need to issue the :probe operation
-
2. Re: How transactions and participants resources are populated ?
claudio4j Sep 1, 2017 10:19 AM (in response to tomjenkinson)I run the probe operation while the entity manager is inserting data into tables, but the transactions resource is not populated. The for-loop to insert data takes some minutes to finish, in hope the transactions resource is populated, but that doesn't happen.
-
3. Re: How transactions and participants resources are populated ?
ochaloup Sep 4, 2017 3:38 AM (in response to claudio4j)Hi claudio4j, the resource '/subsystem=transactions/log-store=log-store/transactions=*/participants=*' is available at time of saving data under transaction log store. That action occurs at time of transaction finishes prepare phase (of 2PC). At time when transaction is actively running it's only counted in statistics but I'm not aware of an (easy) way to get a detailed information about currently running transaction.
-
4. Re: How transactions and participants resources are populated ?
mmusgrov Sep 4, 2017 4:48 AM (in response to ochaloup)1 of 1 people found this helpfulOndra is correct, this feature only exposes logged transactions which have failed. When a transaction prepares a log is written and a probe operation would then cause the transaction and its participants to show up in the console. However, as soon as a successful commit is made the log is removed after which a probe operation would not reveal anything.
The only way to get resource information on unprepared transactions would be to use our experimental transaction analyser (GitHub - jbosstm/transaction-analyser: Monitoring tool for capturing detailed information of completed and in-flight tra… but that only works if you have trace logging enabled and is unsupported.