[jboss-user] [JBoss Cache Users] - JBoss 4.2.2 with TreeCache 1.4.1.SP5: nodes, attributes not

the_olo do-not-reply at jboss.com
Mon Sep 21 05:10:24 EDT 2009


Hi!

I have a clustered TreeCache set up on the standard JBoss 4.2.2 GA release (for caching jBPM-BPEL data).

It seems that the contents of the cache are properly replicated only during the initial state transfer - when a node joins the cluster, the logs show:

2009-09-18 13:44:41,932 INFO  [org.jboss.cache.TreeCache] received the state (size=1024 bytes)
  | 2009-09-18 13:44:41,936 INFO  [org.jboss.cache.TreeCache] received the state (size=1024 bytes)
  | 2009-09-18 13:44:41,939 INFO  [org.jboss.cache.TreeCache] received the state (size=1024 bytes)
  | 2009-09-18 13:44:41,942 INFO  [org.jboss.cache.TreeCache] received the state (size=1024 bytes)
  | 2009-09-18 13:44:41,943 DEBUG [org.jboss.hibernate.jbc.cacheprovider.OptimisticJBCCache] activateCacheRegion(): Region /org/jbpm/graph/def/ProcessDefinition/a
  | ctions is already active
  | 2009-09-18 13:44:41,945 INFO  [org.jboss.cache.TreeCache] received the state (size=1024 bytes)
  | 2009-09-18 13:44:41,946 DEBUG [org.jboss.hibernate.jbc.cacheprovider.OptimisticJBCCache] activateCacheRegion(): Region /org/jbpm/graph/def/ProcessDefinition/d
  | efinitions is already active


While on the node that supplies the state transfer data, I can see in the logs:

2009-09-18 13:44:41,941 INFO  [org.jboss.cache.interceptors.OptimisticNodeInterceptor] read Method _getState; id:19(/org/jbpm/file/def/FileDefinition/processF
  | iles, 400, false, false) called - don't know how to handle, passing on!
  | 2009-09-18 13:44:41,941 INFO  [org.jboss.cache.statetransfer.StateTransferGenerator_140] returning the state for tree rooted in /org/jbpm/file/def/FileDefinit
  | ion/processFiles(1024 bytes)
  | 2009-09-18 13:44:41,944 INFO  [org.jboss.cache.interceptors.OptimisticNodeInterceptor] read Method _getState; id:19(/org/jbpm/bpel/graph/scope/Scope/onEvents,
  |  400, false, false) called - don't know how to handle, passing on!
  | 2009-09-18 13:44:41,944 INFO  [org.jboss.cache.statetransfer.StateTransferGenerator_140] returning the state for tree rooted in /org/jbpm/bpel/graph/scope/Sco
  | pe/onEvents(1024 bytes)
  | 2


During normal operation, however, it seems that cache contents aren't replicated.

I'm looking at the attributes of the "jboss.cache:service=MyTreeCache" MBean.

When I execute a business process on node A, then I can see rapid growth of the "NumberOfAttributes" and "NumberOfNodes" attribute values (until the cache gets saturated).

But the expected synchronous growth on node B doesn't happen. When I do the same on node B, the counts rise on that node, but node A remains uninfluenced.

So I suspect that cache replication does not work. Or maybe it should work that way? Maybe I am looking at the wrong MBean attributes?

Here's the configuration of my TreeCache:


  | <?xml version="1.0" encoding="UTF-8"?>
  | <server>
  |   <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=MyTreeCache">
  |     <depends>jboss:service=Naming</depends>
  |     <depends>jboss:service=TransactionManager</depends>
  | 
  |     <!-- Configure the TransactionManager -->
  |     <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup
  |     </attribute>
  | 
  |     <!--
  |       Node locking scheme :
  |                 PESSIMISTIC (default)
  |                 OPTIMISTIC
  |   -->
  |     <attribute name="NodeLockingScheme">OPTIMISTIC</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>
  | 
  |     <!--
  |     Valid modes are LOCAL REPL_ASYNC REPL_SYNC INVALIDATION_ASYNC INVALIDATION_SYNC
  |   -->
  |     <attribute name="CacheMode">REPL_ASYNC</attribute>
  | 
  |     <!--  Whether each interceptor should have an mbean
  | registered to capture and display its statistics.  -->
  |     <!-- javax.management.AttributeNotFoundException: Attribute 'UseInterceptorMbeans' is not writable -->
  |     <!--
  |   <attribute name="UseInterceptorMbeans">true</attribute>
  |   -->
  | 
  |     <attribute name="UseRegionBasedMarshalling">true</attribute>
  |     <attribute name="InactiveOnStartup">true</attribute>
  | 
  |     <!-- Name of cluster. Needs to be the same for all clusters, in order
  | to find each other -->
  |     <attribute name="ClusterName">${jboss.partition.name:DefaultPartition}-MyTreeCache
  |     </attribute>
  | 
  |     <attribute name="ClusterConfig">
  |       <config>
  |         <UDP mcast_addr="${jboss.partition.udpGroup:228.1.4.5}" mcast_port="${jboss.hapartition.mcast_port:48566}"
  |           tos="8" ucast_recv_buf_size="20000000" ucast_send_buf_size="640000" mcast_recv_buf_size="25000000"
  |           mcast_send_buf_size="640000" loopback="false" discard_incompatible_packets="true" enable_bundling="false"
  |           max_bundle_size="64000" max_bundle_timeout="30" use_incoming_packet_handler="true"
  |           use_outgoing_packet_handler="false" ip_ttl="${jgroups.udp.ip_ttl:2}" down_thread="false" up_thread="false" />
  |         <PING timeout="2000" down_thread="false" up_thread="false" num_initial_members="3" />
  |         <MERGE2 max_interval="100000" down_thread="false" up_thread="false" min_interval="20000" />
  |         <FD_SOCK down_thread="false" up_thread="false" />
  |         <FD timeout="10000" max_tries="5" down_thread="false" up_thread="false" shun="true" />
  |         <VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false" />
  |         <pbcast.NAKACK max_xmit_size="60000" use_mcast_xmit="false" gc_lag="0" retransmit_timeout="300,600,1200,2400,4800"
  |           down_thread="false" up_thread="false" discard_delivered_msgs="true" />
  |         <UNICAST timeout="300,600,1200,2400,3600" down_thread="false" up_thread="false" />
  |         <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000" down_thread="false" up_thread="false"
  |           max_bytes="400000" />
  |         <pbcast.GMS print_local_addr="true" join_timeout="3000" down_thread="false" up_thread="false"
  |           join_retry_timeout="2000" shun="true" view_bundling="true" />
  |         <FRAG2 frag_size="60000" down_thread="false" up_thread="false" />
  |         <pbcast.STATE_TRANSFER down_thread="false" up_thread="false" use_flush="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">5000</attribute>
  |           <attribute name="timeToLiveSeconds">1000</attribute>
  |           <!-- Maximum time an object is kept in cache regardless of idle time -->
  |           <attribute name="maxAgeSeconds">120</attribute>
  |         </region>
  | 
  |         <region name="/org/jboss/data">
  |           <attribute name="maxNodes">5000</attribute>
  |           <attribute name="timeToLiveSeconds">1000</attribute>
  |         </region>
  | 
  |         <region name="/org/jboss/test/data">
  |           <attribute name="maxNodes">5</attribute>
  |           <attribute name="timeToLiveSeconds">4</attribute>
  |         </region>
  | 
  |         <region name="/org/jbpm/graph">
  |           <attribute name="maxNodes">5000</attribute>
  |           <!-- 259200 secs = 3 * 24 hours in order to survive the weekend: -->
  |           <attribute name="timeToLiveSeconds">259200</attribute>
  |         </region>
  |         <region name="/org/jbpm/bpel/graph">
  |           <attribute name="maxNodes">5000</attribute>
  |           <!-- 259200 secs = 3 * 24 hours in order to survive the weekend: -->
  |           <attribute name="timeToLiveSeconds">259200</attribute>
  |         </region>
  |         <region name="/org/jbpm">
  |           <attribute name="maxNodes">10000</attribute>
  |           <attribute name="timeToLiveSeconds">7200</attribute>
  |           <attribute name="maxAgeSeconds">259200</attribute>
  |         </region>
  | 
  |       </config>
  |     </attribute>
  |   </mbean>
  | </server>
  | 
  | I've tried both with REPL_ASYNC and REPL_SYNC CacheMode and the result is the same.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256102#4256102

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256102



More information about the jboss-user mailing list