[jboss-user] [JBossCache] - Re: Jboss Caching issue

bhavranjan do-not-reply at jboss.com
Mon Feb 5 01:30:35 EST 2007


  |  Thanks for ur reply
  | 
  | I have already checked that , here is my confi.xml  files
  | 
  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <!-- ===================================================================== -->
  | <!--                                                                       -->
  | <!--  Sample TreeCache Service Configuration                               -->
  | <!--                                                                       -->
  | <!-- ===================================================================== -->
  | 
  | <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.JBossTransactionManagerLookup</attribute>
  | 
  |       <!--
  |           Node locking level : SERIALIZABLE
  |                                REPEATABLE_READ (default)
  |                                READ_COMMITTED
  |                                READ_UNCOMMITTED
  |                                NONE
  |       -->
  |       <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
  | 
  |       <!--
  |            Valid modes are LOCAL
  |                            REPL_ASYNC
  |                            REPL_SYNC
  |                            INVALIDATION_ASYNC
  |                            INVALIDATION_SYNC
  |       -->
  |       
  | 
  |      <attribute name="CacheMode">LOCAL</attribute>
  | 
  |         <!-- New 1.3.x cache loader config block -->
  |         <attribute name="CacheLoaderConfiguration">
  |             <config>
  |                 <!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
  |                 <passivation>false</passivation>
  |                 <preload>/demo</preload>
  |                 <shared>false</shared>
  | 
  |                 <!-- we can now have multiple cache loaders, which get chained -->
  |                 <cacheloader>
  |                     <class>org.jboss.cache.loader.FileCacheLoader</class>
  |                     <!-- same as the old CacheLoaderConfig attribute -->
  |                     <properties>
  |                         location=/tmp/bhavFileStore
  |                     </properties>
  |                    
  |                     <!-- only one cache loader in the chain may set fetchPersistentState to true.
  |                         An exception is thrown if more than one cache loader sets this to true. -->
  |                     <fetchPersistentState>true</fetchPersistentState>
  |                     <!-- determines whether this cache loader ignores writes - defaults to false. -->
  |                     <ignoreModifications>false</ignoreModifications>
  |                     <!-- if set to true, purges the contents of this cache loader when the cache starts up.
  |                     Defaults to false.  -->
  |                     <purgeOnStartup>false</purgeOnStartup>
  |                 </cacheloader>
  | 
  |                
  | 
  |             </config>
  |  
  |         </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">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. Not supported now. -->
  |       <attribute name="EvictionPolicyClass"></attribute>
  |    </mbean>
  | 
  | <mbean
  | code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
  | name="jboss:service=proxyFactory,type=jrmp,target=factory">
  | <attribute
  | name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
  | <attribute
  | name="TargetName">jboss.cache:service=TreeCache</attribute>
  | <attribute name="JndiName">TreeCache</attribute> <attribute
  | name="InvokeTargetMethod">true</attribute> <attribute
  | name="ExportedInterface">org.jboss.cache.TreeCacheMBean</attribute>
  | <attribute name="ClientInterceptors"> <iterceptors>
  | <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
  | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  | <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  | </iterceptors> </attribute>
  | <depends>jboss:service=invoker,type=jrmp</depends>
  | <depends>jboss.cache:service=TreeCache</depends>
  | </mbean>
  | </server>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011156#4011156

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011156



More information about the jboss-user mailing list