[jboss-cvs] JBossCache/etc/META-INF ...
Jerry Gauthier
jgauthier at novell.com
Wed Sep 6 13:57:40 EDT 2006
User: jerrygauth
Date: 06/09/06 13:57:40
Modified: etc/META-INF
buddyreplication-service.xml
hibernate-recommended-config.xml
interopCurAsync-service.xml
interopCurSync-service.xml
interopPrevAsync-service.xml
interopPrevSync-service.xml
invalidationAsync-service.xml
invalidationSync-service.xml
local-elementsize-eviction-service.xml
local-fifo-eviction-service.xml
local-lfu-eviction-service.xml
local-lru-eviction-service.xml
local-mru-eviction-service.xml
local-passivation-service.xml local-service.xml
mixedPolicy-eviction-service.xml mux-service.xml
node1.xml node2.xml oodb-service.xml
optimal-for-large-cluster-http-session-repl.xml
policyPerRegion-eviction-service.xml
replAsync-optimistic-service.xml
replAsync-service.xml
replAsyncSharedCacheLoader-service.xml
replSync-ChainingCacheLoader-service.xml
replSync-ClusteredCacheLoader-service.xml
replSync-eviction-service.xml
replSync-optimistic-service.xml
replSync-passivation-service.xml
replSync-service.xml tree-service.xml
Log:
JBCACHE-470
Revision Changes Path
1.6 +12 -3 JBossCache/etc/META-INF/buddyreplication-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: buddyreplication-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/buddyreplication-service.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- buddyreplication-service.xml 10 Jul 2006 14:50:03 -0000 1.5
+++ buddyreplication-service.xml 6 Sep 2006 17:57:39 -0000 1.6
@@ -45,16 +45,25 @@
-->
<attribute name="CacheMode">REPL_SYNC</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.6 +12 -3 JBossCache/etc/META-INF/hibernate-recommended-config.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: hibernate-recommended-config.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/hibernate-recommended-config.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- hibernate-recommended-config.xml 11 May 2006 00:01:00 -0000 1.5
+++ hibernate-recommended-config.xml 6 Sep 2006 17:57:39 -0000 1.6
@@ -71,16 +71,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/interopCurAsync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: interopCurAsync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/interopCurAsync-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- interopCurAsync-service.xml 11 May 2006 00:01:00 -0000 1.3
+++ interopCurAsync-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -56,16 +56,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/interopCurSync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: interopCurSync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/interopCurSync-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- interopCurSync-service.xml 11 May 2006 00:01:00 -0000 1.3
+++ interopCurSync-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -57,16 +57,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.3 +12 -3 JBossCache/etc/META-INF/interopPrevAsync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: interopPrevAsync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/interopPrevAsync-service.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- interopPrevAsync-service.xml 22 Feb 2006 05:34:40 -0000 1.2
+++ interopPrevAsync-service.xml 6 Sep 2006 17:57:39 -0000 1.3
@@ -55,16 +55,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.3 +12 -3 JBossCache/etc/META-INF/interopPrevSync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: interopPrevSync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/interopPrevSync-service.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- interopPrevSync-service.xml 22 Feb 2006 05:34:40 -0000 1.2
+++ interopPrevSync-service.xml 6 Sep 2006 17:57:39 -0000 1.3
@@ -55,16 +55,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/invalidationAsync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: invalidationAsync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/invalidationAsync-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- invalidationAsync-service.xml 11 May 2006 00:01:00 -0000 1.3
+++ invalidationAsync-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/invalidationSync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: invalidationSync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/invalidationSync-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- invalidationSync-service.xml 11 May 2006 00:01:00 -0000 1.3
+++ invalidationSync-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.2 +19 -10 JBossCache/etc/META-INF/local-elementsize-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-elementsize-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-elementsize-eviction-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- local-elementsize-eviction-service.xml 7 May 2006 03:34:39 -0000 1.1
+++ local-elementsize-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.2
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/local-fifo-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-fifo-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-fifo-eviction-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- local-fifo-eviction-service.xml 22 Feb 2006 03:06:27 -0000 1.3
+++ local-fifo-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.5 +19 -10 JBossCache/etc/META-INF/local-lfu-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-lfu-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-lfu-eviction-service.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- local-lfu-eviction-service.xml 22 Feb 2006 03:06:27 -0000 1.4
+++ local-lfu-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.5
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/local-lru-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-lru-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-lru-eviction-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- local-lru-eviction-service.xml 9 Apr 2006 12:33:47 -0000 1.3
+++ local-lru-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/local-mru-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-mru-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-mru-eviction-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- local-mru-eviction-service.xml 22 Feb 2006 03:06:27 -0000 1.3
+++ local-mru-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -3 JBossCache/etc/META-INF/local-passivation-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-passivation-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-passivation-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- local-passivation-service.xml 18 Jul 2006 10:47:36 -0000 1.3
+++ local-passivation-service.xml 6 Sep 2006 17:57:39 -0000 1.4
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.8 +12 -3 JBossCache/etc/META-INF/local-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: local-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/local-service.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- local-service.xml 11 May 2006 00:01:00 -0000 1.7
+++ local-service.xml 6 Sep 2006 17:57:39 -0000 1.8
@@ -44,16 +44,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.3 +19 -10 JBossCache/etc/META-INF/mixedPolicy-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: mixedPolicy-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/mixedPolicy-eviction-service.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- mixedPolicy-eviction-service.xml 22 Feb 2006 03:06:27 -0000 1.2
+++ mixedPolicy-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.3
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.2 +2 -2 JBossCache/etc/META-INF/mux-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: mux-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/mux-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- mux-service.xml 17 Aug 2006 14:29:25 -0000 1.1
+++ mux-service.xml 6 Sep 2006 17:57:39 -0000 1.2
@@ -52,8 +52,8 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all nodes in a clusters, in order
+ to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
1.11 +12 -4 JBossCache/etc/META-INF/node1.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: node1.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/node1.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- node1.xml 30 May 2006 18:40:24 -0000 1.10
+++ node1.xml 6 Sep 2006 17:57:39 -0000 1.11
@@ -61,17 +61,25 @@
-->
<attribute name="ReplQueueMaxElements">5</attribute>
-
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.11 +12 -4 JBossCache/etc/META-INF/node2.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: node2.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/node2.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- node2.xml 30 May 2006 18:40:24 -0000 1.10
+++ node2.xml 6 Sep 2006 17:57:39 -0000 1.11
@@ -61,17 +61,25 @@
-->
<attribute name="ReplQueueMaxElements">5</attribute>
-
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.11 +12 -3 JBossCache/etc/META-INF/oodb-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: oodb-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/oodb-service.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- oodb-service.xml 30 May 2006 18:40:24 -0000 1.10
+++ oodb-service.xml 6 Sep 2006 17:57:39 -0000 1.11
@@ -45,16 +45,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.9 +12 -3 JBossCache/etc/META-INF/optimal-for-large-cluster-http-session-repl.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: optimal-for-large-cluster-http-session-repl.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/optimal-for-large-cluster-http-session-repl.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- optimal-for-large-cluster-http-session-repl.xml 30 May 2006 18:40:24 -0000 1.8
+++ optimal-for-large-cluster-http-session-repl.xml 6 Sep 2006 17:57:39 -0000 1.9
@@ -61,16 +61,25 @@
-->
<attribute name="ReplQueueMaxElements">25</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.3 +19 -10 JBossCache/etc/META-INF/policyPerRegion-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: policyPerRegion-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/policyPerRegion-eviction-service.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- policyPerRegion-eviction-service.xml 22 Feb 2006 03:06:27 -0000 1.2
+++ policyPerRegion-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.3
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.9 +12 -3 JBossCache/etc/META-INF/replAsync-optimistic-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replAsync-optimistic-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replAsync-optimistic-service.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- replAsync-optimistic-service.xml 11 May 2006 00:01:00 -0000 1.8
+++ replAsync-optimistic-service.xml 6 Sep 2006 17:57:39 -0000 1.9
@@ -69,16 +69,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.8 +12 -3 JBossCache/etc/META-INF/replAsync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replAsync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replAsync-service.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- replAsync-service.xml 11 May 2006 00:01:00 -0000 1.7
+++ replAsync-service.xml 6 Sep 2006 17:57:39 -0000 1.8
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.10 +12 -3 JBossCache/etc/META-INF/replAsyncSharedCacheLoader-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replAsyncSharedCacheLoader-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replAsyncSharedCacheLoader-service.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- replAsyncSharedCacheLoader-service.xml 30 May 2006 18:40:24 -0000 1.9
+++ replAsyncSharedCacheLoader-service.xml 6 Sep 2006 17:57:39 -0000 1.10
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.9 +12 -3 JBossCache/etc/META-INF/replSync-ChainingCacheLoader-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replSync-ChainingCacheLoader-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replSync-ChainingCacheLoader-service.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- replSync-ChainingCacheLoader-service.xml 30 May 2006 18:40:24 -0000 1.8
+++ replSync-ChainingCacheLoader-service.xml 6 Sep 2006 17:57:39 -0000 1.9
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.8 +12 -3 JBossCache/etc/META-INF/replSync-ClusteredCacheLoader-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replSync-ClusteredCacheLoader-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replSync-ClusteredCacheLoader-service.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- replSync-ClusteredCacheLoader-service.xml 30 May 2006 18:40:24 -0000 1.7
+++ replSync-ClusteredCacheLoader-service.xml 6 Sep 2006 17:57:39 -0000 1.8
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.5 +12 -3 JBossCache/etc/META-INF/replSync-eviction-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replSync-eviction-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replSync-eviction-service.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- replSync-eviction-service.xml 22 Feb 2006 03:06:27 -0000 1.4
+++ replSync-eviction-service.xml 6 Sep 2006 17:57:39 -0000 1.5
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.9 +12 -3 JBossCache/etc/META-INF/replSync-optimistic-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replSync-optimistic-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replSync-optimistic-service.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- replSync-optimistic-service.xml 11 May 2006 00:01:00 -0000 1.8
+++ replSync-optimistic-service.xml 6 Sep 2006 17:57:39 -0000 1.9
@@ -69,16 +69,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.2 +12 -3 JBossCache/etc/META-INF/replSync-passivation-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replSync-passivation-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replSync-passivation-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- replSync-passivation-service.xml 18 Jul 2006 15:36:03 -0000 1.1
+++ replSync-passivation-service.xml 6 Sep 2006 17:57:39 -0000 1.2
@@ -43,16 +43,25 @@
-->
<attribute name="CacheMode">REPL_SYNC</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.10 +12 -3 JBossCache/etc/META-INF/replSync-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: replSync-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/replSync-service.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- replSync-service.xml 11 May 2006 00:01:00 -0000 1.9
+++ replSync-service.xml 6 Sep 2006 17:57:40 -0000 1.10
@@ -59,16 +59,25 @@
-->
<attribute name="ReplQueueMaxElements">0</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
1.4 +12 -4 JBossCache/etc/META-INF/tree-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: tree-service.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/tree-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- tree-service.xml 14 Nov 2005 19:57:41 -0000 1.3
+++ tree-service.xml 6 Sep 2006 17:57:40 -0000 1.4
@@ -26,7 +26,6 @@
-->
<attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
-
<!--
Node locking level : SERIALIZABLE
REPEATABLE_READ (default)
@@ -45,16 +44,25 @@
-->
<attribute name="CacheMode">LOCAL</attribute>
- <!-- Name of cluster. Needs to be the same for all clusters, in order
- to find each other
+ <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
+ cluster in order to find each other.
-->
<attribute name="ClusterName">TreeCache-Cluster</attribute>
+ <!--Uncomment next three statements to enable JGroups multiplexer.
+ This configuration is dependent on the JGroups multiplexer being
+ registered in an MBean server such as JBossAS. -->
+ <!--
+ <depends>jgroups.mux:name=Multiplexer</depends>
+ <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
+ <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
+ -->
+
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
+ ClusterConfig isn't used if the multiplexer is enabled and successfully initialized.
-->
-
<attribute name="ClusterConfig">
<config>
<!-- UDP: if you have a multihomed machine,
More information about the jboss-cvs-commits
mailing list