Can you clarify what it is that you need to know. I don't understand where these
attributes are coming from nor what their values mean.
We do have various beans that we have, in the past, exposed via JMX or via RHQ. For
example, consider the first attribute "core-environment" => .... I guess
this is referring to our CoreEnvironment bean which does have a property called
socketProcessIdPort which we use to facilitate creation of unique ids and it also has a
property called nodeIdentifier which we use to ensure that different recovery managers
don't end up recovering each others transactions. But there are also other properties
in that bean which your snippet does not mention.
The enable-statistics property simply enables metrics gathering for transaction counts
(heuristics, commits etc). Once enabled the statistics can be retrieved from our TxStats
MBean.
Mike
----- Original Message -----
> From: "Heiko Braun"<hbraun(a)redhat.com>
> To:"jboss-as7-dev@lists.jboss.org Development"
<jboss-as7-dev(a)lists.jboss.org>
> Sent: Tuesday, May 10, 2011 9:07:24 AM
> Subject: [jboss-as7-dev] TX subsystem management use cases
>
>
>
> Can anyone shed some light on the management op's for the transaction
> subsystem?
> The attribute names indicate more sophisticated features, like
> statistics.
>
> I would need to know how to work with this data in order expose
> reasonable functionality through the web UI.
>
> [domain@localhost:9999 /]
> /profile=default/subsystem=transactions:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "core-environment" => {
> "socket-binding" => "txn-socket-process-id",
> "node-identifier" => undefined
> },
> "recovery-environment" => {
> "socket-binding" =>
"txn-recovery-environment",
> "status-socket-binding" =>
"txn-status-manager"
> },
> "coordinator-environment" => {
> "enable-statistics" => undefined,
> "default-timeout" => undefined
> },
> "object-store" => {
> "relative-to" => undefined,
> "path" => undefined
> }
> },
> "compensating-operation" => undefined
> }
>