[jboss-user] [JBoss Portal] - JBossCache - org.jboss.cache.lock.TimeoutException: failure

[jChela]

Hi,

I am using JBossCache as standalone and just want to use eviction policy.

Can I turn off TransactionManager? What changes do I need to do in the config file below?

My app is running in JBoss App and has distribution transactions but I don't want JBoss cache to be part of it. My cache is always read only. I left the transaction manager config as-is (see below config) and I am getting: 
org.jboss.cache.lock.TimeoutException: failure acquiring lock

Thanks in advance:


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

<!-- ===================================================================== -->
<!--                                                                       -->
<!--  Sample TreeCache Service Configuration                               -->
<!--                                                                       -->
<!-- ===================================================================== -->



    


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

    

        jboss:service=Naming
        jboss:service=TransactionManager

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


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

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

        <!-- 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: 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="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"/>
                <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" 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="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
        -->
        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


        <!-- Name of the eviction policy class. -->
        org.jboss.cache.eviction.FIFOPolicy
        <!-- Specific eviction policy configurations. This is LRU -->
        
           
              3
              <!-- Cache wide default -->
              
                  5000
              
            
               100000
               60
               100
            
           
        
        
    





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

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