1 Reply Latest reply on Aug 30, 2005 6:30 PM by ben.wang

    Problems with ibmjdk-1.4.2 and JBossCache

    xexecute

      I'm using JBossCache (1.2.3) with ibmjdk-1.4.2.

      While runnung test on the JBossCache (putting objects, in the LOCAL IsolationLevel) the VM problem ossurs.

      While running it in REPL_SYNC/REPL_ASYNC IsolationLevel the following exception was thrown:



      org.jboss.cache.lock.TimeoutException: rsp=sender=172.30.186.107:1121, 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:1762)
      at org.jboss.cache.TreeCache.put(TreeCache.java:1702)



      Is is important to notice that each time new instance of TreeCache is created (despite of previous closing) members list is from the previous instance kept ...

      INFO org.jboss.cache.TreeCache - viewAccepted(): new members: [172.30.186.107:1121, 172.30.186.146:2582, 172.30.186.156:2193, 172.30.186.138:2670, 172.30.186.116:2535, 172.30.186.138:2677]

      To close the TreeCache i call:

      cache.stopService();
      cache.destroyService();
      cache = null;


      What can be the reason of that behaviour ? Does JBossCache work with the IBM VM ???