[jboss-user] [JBoss Cache: Core Edition] - Strange invalidation
dancantong
do-not-reply at jboss.com
Thu Nov 20 05:31:23 EST 2008
Hi!
I'm working with JBoss TreeCache 1.4.1 with Tomcat 5.5. I have two tomcat instances configured with one cache instance each. I have configured cache for cluster invalidation and I'm experiencing the following behaviour. First I insert a cache node in a Tomcat instance. Then, I insert the same cache node (with same FQN and attribute data) in another Tomcat instance. After that, If I query for the cached node in the first Tomcat instance, it says it cannot find the node.
Is this a normal behaviour with cluster invalidation? How can I maintain the same node cached at the same time in both caches instances?
This is the cache configuration file (applied to both cache instances):
<server>
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" />
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
| <mbean code="org.jboss.cache.TreeCache" name="OMADL:name=ThemeAndMediaObjectCache">
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
|
|
| <!-- Configure the TransactionManager -->
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.GenericTransactionManagerLookup</attribute>
|
| <!--
| Node locking scheme :
| PESSIMISTIC (default)
| OPTIMISTIC
| -->
| <attribute name="NodeLockingScheme">PESSIMISTIC</attribute>
|
| <!--
| Node locking isolation level :
| SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
|
| (ignored if NodeLockingScheme is OPTIMISTIC)
| -->
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
|
| <!-- Lock parent before doing node additions/removes -->
| <attribute name="LockParentForChildInsertRemove">true</attribute>
|
| <!-- Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <attribute name="CacheMode">INVALIDATION_ASYNC</attribute>
|
| <!-- Whether each interceptor should have an mbean
| registered to capture and display its statistics. -->
| <attribute name="UseInterceptorMbeans">true</attribute>
|
| <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
| cluster, in order to find each other -->
| <attribute name="ClusterName">OMADLCacheCluster</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">udp</attribute>
| -->
|
| <!-- JGroups protocol stack properties. ClusterConfig isn't used if the
| multiplexer is enabled and successfully initialized. -->
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address
| -->
| <!-- UDP: On Windows machines, because of the media sense feature
| being broken with multicast (even after disabling media sense)
| set the loopback attribute to true
| -->
| <UDP mcast_addr="228.1.2.3" mcast_port="45566" bind_addr="127.0.0.1" ip_ttl="64" ip_mcast="true"
| mcast_send_buf_size="150000" mcast_recv_buf_size="80000" ucast_send_buf_size="150000"
| ucast_recv_buf_size="80000" loopback="false" />
| <PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false" />
| <MERGE2 min_interval="10000" max_interval="20000" />
| <FD shun="true" up_thread="true" down_thread="true" />
| <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false" />
| <pbcast.NAKACK gc_lag="50" max_xmit_size="8192" retransmit_timeout="600,1200,2400,4800" up_thread="false"
| down_thread="false" />
| <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" down_thread="false" />
| <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false" />
| <FRAG frag_size="8192" down_thread="false" up_thread="false" />
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" print_local_addr="true" />
| <pbcast.STATE_TRANSFER up_thread="false" down_thread="false" />
| </config>
| </attribute>
|
| <!-- The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">5000</attribute>
|
| <!-- Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">10000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">15000</attribute>
|
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
|
| <!-- Specific eviction policy configurations. This is LRU -->
| <attribute name="EvictionPolicyConfig">
| <config>
| <attribute name="wakeUpIntervalSeconds">5</attribute>
| <!-- Cache wide default -->
| <region name="/_default_">
| <attribute name="maxNodes">100</attribute>
| <attribute name="timeToLiveSeconds">3600</attribute>
| </region>
|
| <region name="/ThemeInfo">
| <attribute name="maxNodes">10</attribute>
| <attribute name="timeToLiveSeconds">3600</attribute>
| </region>
|
| <region name="/MediaObjectData">
| <attribute name="maxNodes">10</attribute>
| <attribute name="timeToLiveSeconds">3600</attribute>
| </region>
| </config>
| </attribute>
| </mbean>
| </server>
Best regards,
Daniel.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190813#4190813
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190813
More information about the jboss-user
mailing list