[jboss-user] [JBossCache] - Re: Initial State Transfer Failure

alauro do-not-reply at jboss.com
Thu Nov 1 16:25:26 EDT 2007


3rd try's a charm:



&server>
    <!-- ==================================================================== -->
    <!-- Defines TreeCache configuration                                      -->
    <!-- ==================================================================== -->

    

      jboss:service=Naming
      jboss:service=TransactionManager
      jboss.aop:service=AspectDeployer

      <!--
          Configure the TransactionManager
      -->
      org.jboss.cache.BatchModeTransactionManagerLookup

      <!--
          Isolation level : SERIALIZABLE
                            REPEATABLE_READ (default)
                            READ_COMMITTED
                            READ_UNCOMMITTED
                            NONE
      -->
      REPEATABLE_READ

      <!--
           Valid modes are LOCAL
                           REPL_ASYNC
                           REPL_SYNC
                           INVALIDATION_ASYNC
                           INVALIDATION_SYNC
      -->
      REPL_ASYNC

      <!--
          Just used for async repl: use a replication queue
      -->
      false

      <!--
          Replication interval for replication queue (in ms)
      -->
      0

      <!--
          Max number of elements which trigger replication
      -->
      0

      <!-- Name of cluster. Needs to be the same for all clusters, in order
           to find each other
      -->
      TreeCache-Cluster

      <!-- JGroups protocol stack properties. Can also be a URL,
           e.g. file:/home/bela/default.xml
         
      -->

      
          
              <UDP mcast_addr="228.1.2.3" mcast_port="48866"
                  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" bind_addr="192.168.181.190" />
              <PING timeout="2000" num_initial_members="3"
                  up_thread="false" down_thread="false"
                  initial_hosts="192.168.181.191[48866]"/>
              <MERGE2 min_interval="10000" max_interval="20000"/>
              <FD_SOCK/>
              <VERIFY_SUSPECT timeout="1500"
                  up_thread="false" down_thread="false"/>
              <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
                  max_xmit_size="8192" 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="true" down_thread="true"/>
          
      

      <!--
       Whether or not to fetch state on joining a cluster
       NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
      -->
      true

      <!--
          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
      -->
      20000

      <!--
          Number of milliseconds to wait until all responses for a
          synchronous call have been received.
      -->
      20000

      <!-- Max number of milliseconds to wait for a lock acquisition -->
      15000

      <!-- Eviction policy defines how long nodes in defined regions stay -->
      <!-- in cache before being removed. In this case a cache entry can  -->
      <!-- stay in cache w/out any activity for the specified number of   -->
      <!-- seconds. BAM will update timestamp on the record every time    -->
      <!-- an interium accounting record is received. Likewise the record -->
      <!-- will be removed when a accounting stop record is received.     -->
      <!-- So, this policy is used to remove nodes in cases where an      -->
      <!-- accounting stop record is lost.                                -->
      <!--                                                                -->
      <!-- NOTE: the timeToLiveSeconds must be greater than the time      -->
      <!-- used to send interium accouning records. Also /SessionKeys     -->
      <!-- and Sessions must have a timeToLiveSeconds > /SessionKeyIndex  --> 
      <!-- as the indexs have to be removed before the acutal data to     --> 
      <!-- avoid a race condition.                                        --> 

      
         
            5

            <!-- See notes above  -->
            
               0
               3900
            

            <!-- See notes above, time must be > than /SessionKeyuIndex -->
            
               0
               3901
            

            <!-- See notes above, time must be > than /sessionKeyIndex -->
            
               0
               3902
            

            <!-- Default Eviction policy for all other Nodes in cache -->
            
               0
               0
            
         
      

      <!--
         Indicate whether to use marshalling or not. Set this to true if you are running under a scoped
         class loader, e.g., inside an application server. Default is "false".
      -->
      false
      false
    





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

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



More information about the jboss-user mailing list