3 Replies Latest reply on Oct 3, 2005 1:33 PM by Manik Surtani

    org.jboss.cache.lock.TimeoutException: rsp=sender=192.168.10

    stelang stelang Newbie

      Hi,
      I am getting the foll. exception..
      Setup: weblogic6.1, j2sdk1.4.1_04, JBossCache-1.2.3
      Exception:
      org.jboss.cache.lock.TimeoutException: rsp=sender=192.168.102.41:2451, retval=null, received=false, suspecte
      d=false
      [java] at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2205)
      [java] at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2227)
      [java] at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.jav
      a:120)
      [java] at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:85)
      [java] at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3116)
      [java] at org.jboss.cache.TreeCache.put(TreeCache.java:1762)
      [java] at org.jboss.cache.TreeCache.put(TreeCache.java:1702)
      [java] at org.jboss.cache.tests.transaction.SonalTxn1.testConfigure(SonalTxn1.java:96)
      [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      [java] at java.lang.reflect.Method.invoke(Method.java:324)
      [java] at junit.framework.TestCase.runTest(TestCase.java:154)
      [java] at junit.framework.TestCase.runBare(TestCase.java:127)
      [java] at junit.framework.TestResult$1.protect(TestResult.java:106)

      [java] at junit.framework.TestResult.runProtected(TestResult.java:124)
      [java] at junit.framework.TestResult.run(TestResult.java:109)
      [java] at junit.framework.TestCase.run(TestCase.java:118)
      [java] at junit.framework.TestSuite.runTest(TestSuite.java:208)
      [java] at junit.framework.TestSuite.run(TestSuite.java:203)
      [java] Time: 44.032


      My configuration file is:


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





      jboss:service=Naming
      jboss:service=TransactionManager

      <!--
      Configure the TransactionManager-->

      org.jboss.cache.GenericTransactionManagerLookup

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

      REPEATABLE_READ
      REPL_SYNC

      false
      0
      0

      TreeCache-Cluster

      org.jboss.cache.loader.RpcDelegatingCacheLoader

      false

      true




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







      Really appreciate any help or suggestions. Thanks.

        • 1. Re: org.jboss.cache.lock.TimeoutException: rsp=sender=192.16
          Manik Surtani Master

          Hi.

          The conf file you pasted in your posting is not visible. Pls post xml snippets within [ code ] and [ /code ] tags.

          Also, I thought WL 6.x only ran on Java 1.3.1 and they had backward compatibility issues with newer jdks? I could be wrong; what SP level of WL 6.1 are you on?

          • 2. Re: org.jboss.cache.lock.TimeoutException: rsp=sender=192.16
            stelang stelang Newbie

            I am using SP level 4.

            <?xml version="1.0" encoding="UTF-8"?>
            
            <server>
            
             <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
            
            
             <!-- ==================================================================== -->
             <!-- Defines TreeCache configuration -->
             <!-- ==================================================================== -->
            
             <mbean code="org.jboss.cache.TreeCache"
             name="jboss.cache:service=TreeCache">
            
             <depends>jboss:service=Naming</depends>
             <depends>jboss:service=TransactionManager</depends>
            
             <!--
             Configure the TransactionManager-->
            
             <attribute name="TransactionManagerLookupClass">org.jboss.cache.GenericTransactionManagerLookup</attribute>
            
             <!--
             Isolation level : SERIALIZABLE
             REPEATABLE_READ (default)
             READ_COMMITTED
             READ_UNCOMMITTED
             NONE-->
            
             <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
            
             <!--
             Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC
             -->
             <attribute name="CacheMode">REPL_SYNC</attribute>
            
             <!--
             Just used for async repl: use a replication queue
             -->
             <attribute name="UseReplQueue">false</attribute>
            
             <!--
             Replication interval for replication queue (in ms)
             -->
             <attribute name="ReplQueueInterval">0</attribute>
            
             <!--
             Max number of elements which trigger replication
             -->
             <attribute name="ReplQueueMaxElements">0</attribute>
            
             <!-- Name of cluster. Needs to be the same for all clusters, in order
             to find each other
             -->
             <attribute name="ClusterName">TreeCache-Cluster</attribute>
            
             <!-- JGroups protocol stack properties. Can also be a URL,
             e.g. file:/home/bela/default.xml
             <attribute name="ClusterProperties"></attribute>-->
            
            
             <attribute name="CacheLoaderClass">org.jboss.cache.loader.RpcDelegatingCacheLoader</attribute>
            
             <attribute name="CacheLoaderShared">false</attribute>
             <attribute name="CacheLoaderPreload"></attribute>
             <attribute name="CacheLoaderFetchTransientState">true</attribute>
            
            
             <attribute name="ClusterConfig">
             <config>
             <!-- UDP: if you have a multihomed machine,
             set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
             -->
             <!-- 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" />-->
             <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"/>
             </config>
             </attribute>
            
             <!--
             Whether or not to fetch state on joining a cluster
             -->
             <attribute name="FetchStateOnStartup">true</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>
             </region>
             </config>
             </attribute>
             </mbean>
            
            
             <!-- Uncomment to get a graphical view of the TreeCache MBean above -->
             <!-- <mbean code="org.jboss.cache.TreeCacheView" name="jboss.cache:service=TreeCacheView">-->
             <!-- <depends>jboss.cache:service=TreeCache</depends>-->
             <!-- <attribute name="CacheService">jboss.cache:service=TreeCache</attribute>-->
             <!-- </mbean>-->
            
            
            </server>
            
            

            Thanks

            • 3. Re: org.jboss.cache.lock.TimeoutException: rsp=sender=192.16
              Manik Surtani Master

              Hi there

              When do you get this error?

              - Does this happen every time you try to do a put() on one instance?
              - What are the other instances doing at this time?
              - How many nodes have you got in your cluster?
              - Are they all on the same LAN, and what sort of network connectivity have you got linking the nodes?

              Cheers,
              Manik