1 Reply Latest reply on Jan 17, 2007 7:39 AM by Ben Wang

    PojoCache Setup

    Vinutha GR Newbie


      I new to Jboss as well as Jboss Cache. I am trying to set the JBossCache (PojoCache) in Jboss AS which has Jboss Portal.

      Following are the steps.

      Added the following pojocache-service.xml under deploy directory.

      <?xml version="1.0" encoding="UTF-8"?>
      <!-- ===================================================================== -->
      <!-- -->
      <!-- Sample PojoCache Service Configuration -->
      <!-- -->
      <!-- ===================================================================== -->
       <!-- Used inside JBoss AS -->
       <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
       <!-- ==================================================================== -->
       <!-- Defines configuration -->
       <!-- ==================================================================== -->
       <mbean code="org.jboss.cache.aop.PojoCache"
       <!-- Used inside JBoss AS -->
       Configure the TransactionManager
       <attribute name="TransactionManagerLookupClass">org.jboss.cache.DummyTransactionManagerLookup</attribute>
       Node locking scheme:
       PESSIMISTIC (default)
       <attribute name="NodeLockingScheme">PESSIMISTIC</attribute>
       Note that this attribute is IGNORED if your NodeLockingScheme above is OPTIMISTIC.
       Isolation level : SERIALIZABLE
       REPEATABLE_READ (default)
       <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
       Valid modes are LOCAL
       <attribute name="CacheMode">REPL_SYNC</attribute>
       <!-- Name of cluster. Needs to be the same for all clusters, in order
       to find each other
       <attribute name="ClusterName">Sample-Cluster</attribute>
       <!-- JGroups protocol stack properties. Can also be a URL,
       e.g. file:/home/bela/default.xml
       <attribute name="ClusterProperties"></attribute>
       <attribute name="ClusterConfig">
       <!-- 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="" mcast_port="45577"
       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"
       <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"
       up_thread="false" down_thread="false"/>
       <pbcast.STABLE desired_avg_gossip="20000"
       up_thread="false" down_thread="false"/>
       <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10"
       <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
       <attribute name="InitialStateRetrievalTimeout">20000</attribute>
       Number of milliseconds to wait until all responses for a
       synchronous call have been received.
       <attribute name="SyncReplTimeout">15000</attribute>
       <!-- Max number of milliseconds to wait for a lock acquisition -->
       <attribute name="LockAcquisitionTimeout">10000</attribute>
       <attribute name="EvictionPolicyClass"></attribute>
       <!-- Name of the eviction policy class. We have commented it off to disable eviction.
       <attribute name="EvictionPolicyClass">org.jboss.cache.aop.eviction.AopLRUPolicy</attribute>
       <!-- Specific eviction policy configurations. This is LRU -->
       <attribute name="EvictionPolicyConfig">
       <attribute name="wakeUpIntervalSeconds">5</attribute>
       <!-- Cache wide default -->
       <region name="/_default_">
       <attribute name="maxNodes">5000</attribute>
       <attribute name="timeToLiveSeconds">1000</attribute>
       <region name="/aop">
       <attribute name="maxNodes">5</attribute>
       <attribute name="timeToLiveSeconds">4</attribute>
       <region name="/pojo">
       <attribute name="maxNodes">100</attribute>
       <attribute name="timeToLiveSeconds">4</attribute>
       <region name="/testMaxNode">
       <attribute name="maxNodes">4</attribute>
       <attribute name="timeToLiveSeconds">100</attribute>

      Then I have added the jboss-aop.xml under the XXX.war/WEB-INF/ folder

      <?xml version="1.0" encoding="UTF-8"?>
       This is JBossAop way of declaring every field in Address has a hook
       for both get and set.
       <prepare expr="field(* $instanceof{org.jboss.cache.aop.test.Person}->*)" />

      I am using the following test.jsp to test the same.

      MBeanServer server=MBeanServerLocator.locateJBoss();
      TreeCacheMBean cache;
      cache=(TreeCacheMBean)MBeanProxyExt.create(TreeCacheMBean.class, "jboss.cache:service=testPojoCache", server);
      String output1 = (String) cache.get("cache.test","1");
      out.println("</br>cache.test = " + output1);
      Person per= new Person();
      output2 = (String) cache.get("cache.mvn","Person");
      out.println("</br>cache.mvn= " + output2);

      This works fine, but anychanges to the person object are not getting update in the cache.

      I think adding the jboss-aop.xml under the WEB-INF folder alone doesnt solve the issue. What else has to be done?

      Please Help.

        • 1. Re: PojoCache Setup
          Ben Wang Master

          Looks like you are just using the plain cache api, e.g., put and get. In this case, it should work even without jboss-aop.xml. So can you double check that your system with mcast works? If it does, can you try out the TreeCache? If you need troubleshooting, you can go to jboss.org/wiki to look under jbosscache.