[jbossts-issues] [JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown

Michael Musgrove (JIRA) issues at jboss.org
Fri Oct 17 05:56:35 EDT 2014


    [ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012789#comment-13012789 ] 

Michael Musgrove commented on JBTM-2270:
----------------------------------------

More comments:

* In the JTS case, the participant record often resides in a different object store from the transaction log so it you would need tooling that can span multiple stores in order to implement the requested feature.
* We do have a JMX interface to the object store so that would need to be used to look at remote logs but the JMX server would need to be running.
* Something needs to tell the tooling which object stores to look at (which is not a trivial requirement). 

Also, we have about 30 record types. Up until now we have added tooling support on an adhoc basis for records that are of most interest. We really need to add another method to the record interface to enforce developers to take tooling into account when they add new records.

>  When expose-all-logs is used with JTS then no participant for transaction is shown
> -----------------------------------------------------------------------------------
>
>                 Key: JBTM-2270
>                 URL: https://issues.jboss.org/browse/JBTM-2270
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: JTS
>    Affects Versions: 4.17.23
>            Reporter: Ondřej Chaloupka
>            Assignee: Gytis Trikleris
>             Fix For: 6.0.0
>
>
> When expose-all-logs is set to true I'm not able to get any participants of the listed transaction.
> This is log from operation to get type of transaction and then see all participants.
> Reading type of the transaction:
> Succesful management operation {
>     "operation" => "read-attribute",
>     "address" => [
>         ("subsystem" => "transactions"),
>         ("log-store" => "log-store"),
>         ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c")
>     ],
>     "name" => "type"
> } with result {
>     "outcome" => "success",
>     "result" => "CosTransactions/XAResourceRecord"
> }
> Getting participants:
> Succesful management operation {
>     "operation" => "read-children-names",
>     "address" => [
>         ("subsystem" => "transactions"),
>         ("log-store" => "log-store"),
>         ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c")
>     ],
>     "child-type" => "participants"
> } with result {
>     "outcome" => "success",
>     "result" => []
> }



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)



More information about the jbossts-issues mailing list