[jboss-user] [JBossCache] - Re: Node clear method bug or problem in my way to use it.

[pitoui]

treecache.xml
<?xml version="1.0" encoding="UTF-8" ?>

  

  <!--  ====================================================================  -->
  <!--  Defines TreeCache configuration                                       -->
  <!--  ====================================================================  -->
  
    jboss:service=Naming
    jboss:service=TransactionManager


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

	<!-- 
			Node locking scheme : 
								PESSIMISTIC (default)
								OPTIMISTIC 
	-->
	PESSIMISTIC		
<!--
            Node locking isolation level : 
								 SERIALIZABLE
                                 REPEATABLE_READ (default)
                                 READ_COMMITTED
                                 READ_UNCOMMITTED
                                 NONE

			(ignored if NodeLockingScheme is OPTIMISTIC)
    -->
    REPEATABLE_READ

    <!--     Valid modes are LOCAL
                             REPL_ASYNC
                             REPL_SYNC
                             INVALIDATION_ASYNC
                             INVALIDATION_SYNC
    -->
    LOCAL
    
    <!--  Whether each interceptor should have an mbean
        registered to capture and display its statistics.  -->
    true

    <!-- Name of cluster. Needs to be the same for all clusters, in order
             to find each other -->
    JBoss-Cache-Cluster
	 
      
        <!-- 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" 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" />
      
    

    <!--    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
    -->
    5000
	 <!--    Number of milliseconds to wait until all responses for a
            synchronous call have been received.
    -->
    10000

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

    <!--  Name of the eviction policy class. -->
    org.jboss.cache.eviction.LRUPolicy

    <!--  Specific eviction policy configurations. This is LRU -->
    
      
        5
        <!--  Cache wide default -->
        
         5000
         1000
         <!-- Maximum time an object is kept in cache regardless of idle time -->
         120
       

       
         5000
         1000
       

       
         5
         4
       
      
    
	 <!-- New 1.3.x cache loader config block -->
        
            
                <!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
                false
                
                false

                <!-- we can now have multiple cache loaders, which get chained -->
                
                    org.jboss.cache.loader.FileCacheLoader
                    <!-- same as the old CacheLoaderConfig attribute -->
                    
                        location=c:\dev\jbosscache
                    
                    <!-- whether the cache loader writes are asynchronous -->
                    false
                    <!-- only one cache loader in the chain may set fetchPersistentState to true.
                        An exception is thrown if more than one cache loader sets this to true. -->
                    true
                    <!-- determines whether this cache loader ignores writes - defaults to false. -->
                    false
                    <!-- if set to true, purges the contents of this cache loader when the cache starts up.
                    Defaults to false.  -->
                    false
                

<!--                
                    org.jboss.cache.loader.JDBCCacheLoader
                    
                        cache.jdbc.driver=com.mysql.jdbc.Driver
                        cache.jdbc.url=jdbc:mysql://localhost:3306/jbossdb
                        cache.jdbc.user=root
                        cache.jdbc.password=
                    
                    true
                    false
                    true
                    false
                
-->
            
        


  
  

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

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