[jboss-svn-commits] JBL Code SVN: r30577 - in labs/jbosstm/trunk: ArjunaJTS and 1 other directory.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Dec 10 05:52:46 EST 2009
Author: mmusgrov
Date: 2009-12-10 05:52:46 -0500 (Thu, 10 Dec 2009)
New Revision: 30577
Modified:
labs/jbosstm/trunk/ArjunaJTA/INSTALL
labs/jbosstm/trunk/ArjunaJTS/INSTALL
Log:
Adds a section on JMX instrumentation of the Object Store.
JBTM-660
Modified: labs/jbosstm/trunk/ArjunaJTA/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/INSTALL 2009-12-10 09:45:42 UTC (rev 30576)
+++ labs/jbosstm/trunk/ArjunaJTA/INSTALL 2009-12-10 10:52:46 UTC (rev 30577)
@@ -158,10 +158,41 @@
Embedded Tools
--------------
+JMX Instrumentation
+-------------------
-Deployment
-----------
+With this release it is now possible to monitor the transaction Object
+Store using JMX. Monitoring the Object Store is useful for trouble
+shooting problems that occur when transactions are committed (it does
+not expose transactions prior to commit). The JMX instrumentation
+(of the ObjectStore) is a new feature and is not necessarily suitable
+for monitoring production systems.
+In any compliant JMX browser (such as jconsole) there should appear an
+MBean with the name
+ jboss.jta:type=ObjectStore,id=<id>
+This MBean corresponds to the object store and provides a naming context
+for other MBeans (for example in a JMX client such as jconsole the MBeans
+will be displayed in the form of a tree control). The various MBeans
+corresponding to this ObjectStore will have names prefixed by this
+'top level' MBean. Each MBean also exposes a 'refresh' operation
+that causes the instrumentation to check whether any new ObjectStore
+records have been created or whether old ones have been removed.
+
+If JBossTS is deployed in the JBoss application server then JMX
+instrumentation of the ObjectStore is enabled by default. It can be disabled
+by setting the property jmxEnabled on the ObjectStoreEnvironmentBean in the
+transaction-jboss-beans.xml file. The property only effects ObjectStore
+MBeans (it will be renamed to something more specific in the next release).
+
+When JBossTS is deployed stand alone you need to create the 'top level'
+MBean programmatically by calling the following static Java method:
+
+com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreTypeBean::getObjectStoreBrowserBean()
+
+Tools Deployment
+----------------
+
Embedded tools is an applet that runs in proccess with the AS which
includes an interface for inspecting transactions. It is deployed as
a service archive and can be found in the product install directory:
Modified: labs/jbosstm/trunk/ArjunaJTS/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/INSTALL 2009-12-10 09:45:42 UTC (rev 30576)
+++ labs/jbosstm/trunk/ArjunaJTS/INSTALL 2009-12-10 10:52:46 UTC (rev 30577)
@@ -171,9 +171,41 @@
Embedded Tools
--------------
-Deployment
-----------
+JMX Instrumentation
+-------------------
+With this release it is now possible to monitor the transaction Object
+Store using JMX. Monitoring the Object Store is useful for trouble
+shooting problems that occur when transactions are committed (it does
+not expose transactions prior to commit). The JMX instrumentation
+(of the ObjectStore) is a new feature and is not necessarily suitable
+for monitoring production systems.
+
+In any compliant JMX browser (such as jconsole) there should appear an
+MBean with the name
+ jboss.jta:type=ObjectStore,id=<id>
+This MBean corresponds to the object store and provides a naming context
+for other MBeans (for example in a JMX client such as jconsole the MBeans
+will be displayed in the form of a tree control). The various MBeans
+corresponding to this ObjectStore will have names prefixed by this
+'top level' MBean. Each MBean also exposes a 'refresh' operation
+that causes the instrumentation to check whether any new ObjectStore
+records have been created or whether old ones have been removed.
+
+If JBossTS is deployed in the JBoss application server then JMX
+instrumentation of the ObjectStore is enabled by default. It can be disabled
+by setting the property jmxEnabled on the ObjectStoreEnvironmentBean in the
+transaction-jboss-beans.xml file. The property only effects ObjectStore
+MBeans (it will be renamed to something more specific in the next release).
+
+When JBossTS is deployed stand alone you need to create the 'top level'
+MBean programmatically by calling the following static Java method:
+
+com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreTypeBean::getObjectStoreBrowserBean()
+
+Tools Deployment
+----------------
+
Embedded tools is an applet that runs in proccess with the AS which
includes an interface for inspecting transactions. It is deployed as
a service archive and can be found in the product install directory:
More information about the jboss-svn-commits
mailing list