1 Reply Latest reply on Mar 19, 2008 1:53 PM by Tom Goring

    How to do the JbossCache

    Thiagu Mariappan Novice

      Hai every one,

      I need to display 1000 records in a dataTable . I use the JbossCache to reduce the page loading time.

      I use the following steps for JbossCache

      • I put jboss-cache.jar and jgroups.jar in my EAR's lib folder

      • then I put treecache.xml file into resources folder

      This is my productList.xhtml code

      <s:cache key="topOrders" region="/TopOrders" enabled="true">
      <rich:dataTable value="#{productList}" var="Product">
      <f:facet name="header">
      <h:outputText value="SubcategoryName" />
      <h:outputText value="Product Name" />
      <h:outputText value="#{Product.subcat}" />
      <h:outputText value="#{Product.name}" />

      This is my treecache.xml code

      <?xml version="1.0" encoding="UTF-8"?>
      <!-- ===================================================================== -->
      <!--                                                                       -->
      <!--  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" name="jboss.cache:service=testPojoCache">
              <!-- 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">LOCAL</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" 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" 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" 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
              <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>
              <!-- 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">5</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="/TopOrders">
                             <attribute name="maxNodes">100</attribute>
                             <attribute name="timeToLiveSeconds">0</attribute>
                             <attribute name="maxAgeSeconds">86400</attribute>

      And my session bean code is

      public class ProductsAction  implements ProductsLocal,Serializable
      String subcategoryName;
      List<TblProducts> productList;
      public String selectFromRequest() {
      productList =em.createQuery("select t from TblProducts t where t.subcat="+ subcategoryName).getResultList();

      I invoke selectFromRequest method when some one clicks the s:link on my home page and also I pass the subcategoryName through f:param. 

      I need to prevent frequent query execution. I don’t know how to implement that. Is there any need for logic changes in my session bean class.

      Any one, please help me.

      Thiagu. M

        • 1. Re: How to do the JbossCache
          Tom Goring Apprentice

          I think your at least missing query.setHint :


                    Query query = em.createQuery("from ConfigValue val where val.configParameter.configKey = ? and val.configSet.configSetId = ? ");
                    query = query.setParameter(1, key);
                    query = query.setParameter(2, configSet.key());
                    query.setHint("org.hibernate.cacheable", true);