[jboss-cvs] JBossCache/docs/JBossCache-UserGuide/en/modules ...
Brian Stansberry
brian.stansberry at jboss.com
Tue May 29 23:07:40 EDT 2007
User: bstansberry
Date: 07/05/29 23:07:40
Modified: docs/JBossCache-UserGuide/en/modules deployment.xml
Log:
First JMX tweaks
Beautification
Revision Changes Path
1.5 +30 -32 JBossCache/docs/JBossCache-UserGuide/en/modules/deployment.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: deployment.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/docs/JBossCache-UserGuide/en/modules/deployment.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- deployment.xml 29 Jan 2007 17:40:35 -0000 1.4
+++ deployment.xml 30 May 2007 03:07:40 -0000 1.5
@@ -52,26 +52,26 @@
<section>
<title>Binding to JNDI</title>
- <para>If JBoss Cache is run inside of JBoss AS (as an MBean), we can bind it
- into JNDI using JrmpProxyFactory, just like any other MBean. Below is an
+ <para>If JBoss Cache is run inside of JBoss AS (as an MBean), we can bind a
+ proxy to it into JNDI using JrmpProxyFactory, just like any other MBean. Below is an
example of how to do this:
<programlisting>
<![CDATA[
- <mbean
- code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
name="mydomain:service=proxyFactory,type=jrmp,target=factory">
- <attribute
- name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
- <attribute
- name="TargetName">jboss.cache:service=Cache</attribute>
- <attribute name="JndiName">MyCache</attribute> <attribute
- name="InvokeTargetMethod">true</attribute> <attribute
- name="ExportedInterface">org.jboss.cache.jmx.CacheJmxWrapperMBean</attribute>
- <attribute name="ClientInterceptors"> <iterceptors>
+
+ <attribute name="InvokerName">jboss:service=invoker,type=unified</attribute>
+ <attribute name="TargetName">jboss.cache:service=Cache</attribute>
+ <attribute name="JndiName">MyCache</attribute>
+ <attribute name="InvokeTargetMethod">true</attribute>
+ <attribute name="ExportedInterface">org.jboss.cache.jmx.CacheJmxWrapperMBean</attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
<interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
- </iterceptors> </attribute>
+ </interceptors>
+ </attribute>
<depends>jboss:service=invoker,type=jrmp</depends>
<depends>jboss.cache:service=Cache</depends>
</mbean>
@@ -88,10 +88,10 @@
of the MBean that needs to be bound into JNDI.
<literal>JndiName</literal>
is the name under which the MBean will be
- bound, and
- <literal>ExportedInterface</literal>
- is the interface name of
- the MBean.
+ bound.
+ </para>
+ <para>Clients (either in-VM or remote) can look up the proxy in JNDI,
+ download the proxy and use it to invoke on the cache.
</para>
</section>
@@ -131,7 +131,7 @@
<para>
JBoss Cache captures statistics in its interceptors and exposes the statistics through interceptor
MBeans. Cache interceptor MBeans are enabled by default; these MBeans can be disabled for a specific cache
- instance through the <literal>UseInterceptorMbeans</literal> configuration attribute. See the
+ instance through the <literal>ExposeManagementStatistics</literal> configuration attribute. See the
<link linkend="configuration_reference">Configuration Reference chapter</link> for further details on
this attribute.
</para>
@@ -139,7 +139,7 @@
Each interceptor's MBean provides an attribute that can be used to disable maintenance of statistics for
that interceptor. Note that the majority of the statistics are provided by the <literal>CacheMgmtInterceptorMBean</literal>
so this MBean is the most significant in this regard. If you want to disable all statistics for performance
- reasons, you should utilize the <literal>UseInterceptorMbeans</literal> configuration setting as this will
+ reasons, you should utilize the <literal>ExposeManagementStatistics</literal> configuration setting as this will
prevent the <literal>CacheMgmtInterceptor</literal> from being included in the cache's interceptor stack
when the cache is started.
</para>
@@ -163,13 +163,12 @@
JBoss Cache users can register a listener to receive cache events described earlier in the <link linkend="api.listener">User API</link>
chapter. Users can alternatively utilize the cache's management information infrastructure to receive these events
via JMX notifications. Cache events are accessible as notifications by registering a <literal>NotificationListener</literal> for the
- <literal>CacheMgmtInterceptorMBean</literal>. This functionality is only available if cache statistics are enabled
- as described in the previously.
+ <literal>CacheJmxWrapper</literal>.
</para>
<para>
See the section in the <link linkend="jmx_reference.notifications">JMX Reference chapter</link> pertaining
- to JMX notifications for a list of notifications that can be received through the <literal>CacheMgmtInterceptorMBean</literal>.
+ to JMX notifications for a list of notifications that can be received through the <literal>CacheJmxWrapper</literal>.
</para>
@@ -189,14 +188,13 @@
// get reference to CacheMgmtInterceptor MBean
String cache_service = "jboss.cache:service=TomcatClusteringCache";
- String mgmt_service = cache_service + ",cache-interceptor=CacheMgmtInterceptor";
- ObjectName mgmt_name = new ObjectName(mgmt_service);
+ ObjectName mgmt_name = new ObjectName(cache_service);
// configure a filter to only receive node created and removed events
filter = new NotificationFilterSupport();
filter.disableAllTypes();
- filter.enableType(CacheMgmtInterceptor.NOTIF_NODE_CREATED);
- filter.enableType(CacheMgmtInterceptor.NOTIF_NODE_REMOVED);
+ filter.enableType(CacheNotificationBroadcaster.NOTIF_NODE_CREATED);
+ filter.enableType(CacheNotificationBroadcaster.NOTIF_NODE_REMOVED);
// register the listener with a filter
// leave the filter null to receive all cache events
More information about the jboss-cvs-commits
mailing list