Author: prabhat.jha(a)jboss.com
Date: 2008-07-02 15:00:53 -0400 (Wed, 02 Jul 2008)
New Revision: 11267
Modified:
branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-core-sar/META-INF/jboss-service.xml
Log:
JBPORTAL-2054 merging clustering config change from 2.6
Modified:
branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-core-sar/META-INF/jboss-service.xml
===================================================================
---
branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-core-sar/META-INF/jboss-service.xml 2008-07-02
15:43:51 UTC (rev 11266)
+++
branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-core-sar/META-INF/jboss-service.xml 2008-07-02
19:00:53 UTC (rev 11267)
@@ -379,6 +379,31 @@
<depends optional-attribute-name="ThemeService"
proxy-type="attribute">portal:service=ThemeService</depends>
</mbean>
+ <!--
+ Node locking scheme possible values (NodeLockingScheme attribute):
+ OPTIMISTIC
+ PESSIMISTIC (default)
+
+
+ Isolation level possible values (IsolationLevel attribute):
+ SERIALIZABLE
+ REPEATABLE_READ (default)
+ READ_COMMITTED
+ READ_UNCOMMITTED
+ NONE
+ Note that this attribute is IGNORED if your NodeLockingScheme attribute is set at
OPTIMISTIC.
+
+ Cache modes possible values (CacheMode attribute):
+ LOCAL
+ REPL_ASYNC
+ REPL_SYNC
+ INVALIDATION_ASYNC
+ INVALIDATION_SYNC
+
+ If you use REPL_SYNC and a UDP-based ClusterConfig we recommend you comment out the
FC (flow control)
+ protocol in the ClusterConfig section below.
+ -->
+
<!--
| Uncomment in clustered mode : replicated cache for hibernate
@portal.single.xml.close@
@@ -391,7 +416,7 @@
org.jboss.cache.JBossTransactionManagerLookup
</attribute>
- <attribute name="NodeLockingScheme">OPTIMISTIC</attribute>
+ <attribute name="NodeLockingScheme">PESSIMISTIC</attribute>
<attribute name="IsolationLevel">REPEATABLE_READ</attribute>
<attribute name="CacheMode">REPL_SYNC</attribute>