2 Replies Latest reply on Aug 26, 2005 2:52 AM by Alexander Kistanov

    Problems with JBossCache

    Alexander Kistanov Newbie

      Hello, I've met the following problem using JBoss cache. My servlet works with 3 instances of JBoss cache for different purposes. It started on two different computers. When I was testing it I stopped and started application one by another. Afte several restarts I allways got error:
      Caused by: org.jboss.cache.lock.TimeoutException: rsp=sender=11.10.77.77:35744, retval=null, received=false, suspected=false
      at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2205)
      at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2227)
      at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:120)
      at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:85)
      at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3116)
      at org.jboss.cache.TreeCache.put(TreeCache.java:1687)
      at org.jboss.cache.TreeCache.put(TreeCache.java:1671)

      And this error occures after each invocation of put method. It looks like "deadlock" problem already described on this forum. The only way to stop exceptions is to stop both servers wait some time and to start them again. If both servers starts right away after stop then error doesnt disappear. So the questions:

      1) Does JBossCache store its state somewhere (on the file system for example) by default?
      2) Can we correctly detect that we have deadlock?
      3) Can we fix it in runtime or even avoid it?

      Thanks in advance.