[jboss-as7-dev] TX subsystem management use cases

[Brian Stansberry]

On 5/13/11 3:53 AM, Heiko Braun wrote:
>
> Can you add the requirements and related issue here, please:
>
> https://issues.jboss.org/browse/AS7-769
>
>
> I guess all we currently speaks about goes beyond AS 7.0.Final?
>

Exposing the TxStats stuff can be done in 7.0. The object is available, 
so the transaction integration module can access it. The removal of 
static methods Michael talks about will be in a major JBoss TS release, 
and moving to that will require internal changes in the AS's 
transactions integration module anyway.

> Ike
>
> On May 12, 2011, at 6:36 PM, Michael Musgrove wrote:
>
>> Yes that will be OK in the medium term.
>>
>> In the longer term (possibly in release 5.x which is at least a year
>> away) we will need to support multiple transaction managers in the same
>> VM and will need to deprecate most of our static methods.
>>
>> We also have an MBean for exposing the transaction logs - it would be
>> highly desirable to expose these via the management console
>> (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser). However, the
>> implementation requires the presence of an MBeanServer.
>>
>>> I just poked, and I see there is a TxStats.getInstance() method. Is that
>>> a valid API for accessing this?
>>>
>>> On 5/12/11 10:25 AM, Michael Musgrove wrote:
>>>> Can you give me an example of what other projects are providing you with
>>>> or indicate what you prefer. Then I can look into adding it.
>>>>
>>>> BTW AS7 will be consuming JBOSSTS_4_14_0_Final so what is the process
>>>> for making changes.
>>>>
>>>>> Can these TxStats be accessed via something other than JMX? If at all
>>>>> possible I want the AS management layer (in the AS transactions module)
>>>>> to not rely on JMX to pull data from subsystems.
>>>>>
>>>>> On 5/11/11 9:42 AM, Michael Musgrove wrote:
>>>>>> 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 at redhat.com>
>>>>>>>>      To:"jboss-as7-dev at lists.jboss.org Development"<jboss-as7-dev at 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 at 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
>>>>>>>>      }
>>>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat