[jboss-cvs] JBossAS SVN: r93133 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Sep 2 11:41:55 EDT 2009
Author: pferraro
Date: 2009-09-02 11:41:55 -0400 (Wed, 02 Sep 2009)
New Revision: 93133
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml
Log:
[JBPAPP-2640] Sync'ed config file content, minor updates
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml 2009-09-02 15:39:54 UTC (rev 93132)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml 2009-09-02 15:41:55 UTC (rev 93133)
@@ -14,7 +14,8 @@
<section id="clustering-session-slsb30">
<title>Stateless Session Bean in EJB 3.0</title>
<para>
- Clustering stateless session beans is most probably the easiest case: as no state is involved, calls can be load-balanced on any participating node (i.e. any node that has this specific bean deployed) of the cluster.
+ Clustering stateless session beans is probably the easiest case since no state is involved.
+ Calls can be load balanced to any participating node (i.e. any node that has this specific bean deployed) of the cluster.
</para>
<para>
To cluster a stateless session bean in EJB 3.0, all you need to do is to annotate the bean class with the <literal>@Clustered</literal> annotation.
@@ -61,7 +62,7 @@
<note>
<para>
- The <literal><clustered>true</clustered></literal> element is really just an alias for the <literal><configuration-name>Clustered Stateless SessionBean</configuration-name></literal> element in the conf/standard-jboss.xml file.
+ The <literal><clustered>true</clustered></literal> element is really just an alias for the <literal><container-name>Clustered Stateless SessionBean</container-name></literal> element in the conf/standardjboss.xml file.
</para>
</note>
@@ -116,7 +117,7 @@
]]></programlisting>
<itemizedlist>
- <listitem><para><literal>name</literal> specifies the name of a cache configuration registered with the <literal>CacheManager</literal> service discussed in <xref linkend="clustering-blocks-jbc-cachemanager"/>. By default, the <literal>sfsb-cache</literal> configuration will be used.</para></listitem>
+ <listitem><para><literal>name</literal> specifies the name of a cache configuration registered with the <literal>CacheManager</literal> service discussed in <xref linkend="sfsb-jbc-cachemanager"/>. By default, the <literal>sfsb-cache</literal> configuration will be used.</para></listitem>
<listitem><para><literal>maxSize</literal> specifies the maximum number of beans that can cached before the cache should start passivating beans, using an LRU algorithm.</para></listitem>
<listitem><para><literal>idleTimeoutSeconds</literal> specifies the max period of time a bean can go unused before the cache should passivate it (irregardless of whether maxSize beans are cached.)</para></listitem>
<listitem><para><literal>removalTimeoutSeconds</literal> specifies the max period of time a bean can go unused before the cache should remove it altogether.</para></listitem>
@@ -177,7 +178,7 @@
</para>
</section>
- <section>
+ <section id="sfsb-jbc-cachemanager">
<title>CacheManager service configuration</title>
<para>
JBoss Cache provides the session state replication service for EJB 3.0 stateful session beans.
@@ -200,6 +201,7 @@
<property name="nodeLockingScheme">PESSIMISTIC</property>
<property name="isolationLevel">REPEATABLE_READ</property>
+ <property name="useLockStriping">false</property>
<property name="cacheMode">REPL_ASYNC</property>
<!--
@@ -473,51 +475,49 @@
<section>
<title>The HASessionState service configuration</title>
<para>
- The <literal>HASessionState</literal> service MBean is defined in the
- <code>all/deploy/cluster-service.xml</code> file.</para>
+ The <literal>HASessionStateService</literal> bean is defined in the
+ <code>all/deploy/cluster/ha-legacy-jboss-beans.xml</code> file.</para>
<programlisting><![CDATA[
-<mbean code="org.jboss.ha.hasessionstate.server.HASessionStateService" name="jboss:service=HASessionState">
- <depends>jboss:service=Naming</depends>
- <!--
- We now inject the partition into the HAJNDI service instead
- of requiring that the partition name be passed
- -->
- <depends optional-attribute-name="ClusterPartition" proxy-type="attribute">
- jboss:service=${jboss.partition.name:DefaultPartition}
- </depends>
+<bean name="HASessionStateService"
+ class="org.jboss.ha.hasessionstate.server.HASessionStateService">
+
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=HASessionState", exposedInterface=org.jboss.ha.hasessionstate.server.HASessionStateServiceMBean.class, registerDirectly=true)</annotation>
+
+ <!-- Partition used for group RPCs -->
+ <property name="HAPartition"><inject bean="HAPartition"/></property>
+
<!-- JNDI name under which the service is bound -->
- <attribute name="JndiName">/HASessionState/Default</attribute>
- <!--
- Max delay before cleaning unreclaimed state.
- Defaults to 30*60*1000 => 30 minutes
- -->
- <attribute name="BeanCleaningDelay">0</attribute>
-</mbean>
+ <property name="jndiName">/HASessionState/Default</property>
+ <!-- Max delay before cleaning unreclaimed state.
+ Defaults to 30*60*1000 => 30 minutes -->
+ <property name="beanCleaningDelay">0</property>
+
+</bean>
]]></programlisting>
- <para>The configuration attributes in the <literal>HASessionState</literal> MBean are listed below.</para>
+ <para>The configuration attributes in the <literal>HASessionStateService</literal> bean are listed below.</para>
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">ClusterPartition</emphasis> is a required attribute to inject the HAPartition service that HA-JNDI uses for intra-cluster communication.
+ <emphasis role="bold">HAPartition</emphasis> is a required attribute to inject the HAPartition service that HA-JNDI uses for intra-cluster communication.
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">JndiName</emphasis> is an optional attribute to specify the JNDI
- name under which this <literal>HASessionState</literal> service is bound. The default
+ <emphasis role="bold">jndiName</emphasis> is an optional attribute to specify the JNDI
+ name under which this <literal>HASessionStateService</literal> bean is bound. The default
value is <literal>/HAPartition/Default</literal>.
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">BeanCleaningDelay</emphasis> is an optional attribute to specify
- the number of miliseconds after which the <literal>HASessionState</literal> service can
+ <emphasis role="bold">beanCleaningDelay</emphasis> is an optional attribute to specify
+ the number of miliseconds after which the <literal>HASessionStateService</literal> bean can
clean a state that has not been modified. If a node, owning a bean, crashes, its brother
node will take ownership of this bean. Nevertheless, the container cache of the brother
node will not know about it (because it has never seen it before) and will never delete
according to the cleaning settings of the bean. That is why the
- <literal>HASessionState</literal> service needs to do this cleanup sometimes. The
+ <literal>HASessionStateService</literal> bean needs to do this cleanup sometimes. The
default value is <literal>30*60*1000</literal> milliseconds (i.e., 30 minutes).
</para>
</listitem>
More information about the jboss-cvs-commits
mailing list