[jboss-user] [JBoss Cache: Core Edition] - Re: Endless loop trying to obtain lock in 1.4.1.SP9

BradleyDouglas do-not-reply at jboss.com
Tue Aug 26 03:02:20 EDT 2008


Hey - thanks for the quick response.

Bah! typo, I've upgraded us to 2.1.1.GA:

anonymous wrote : 
  | C:\synyati\workspace\spurwing_jboss\lib\runtime\cache>java -jar jbosscache-core-2.1.1.GA.jar
  | 
  | Version:        2.1.1.GA
  | Codename:       Alegrias
  | History:        (see http://jira.jboss.com/jira/browse/JBCACHE for details)
  | 

It would be very cool if the version # was output in the logs (as many tools do) so it was 100% certain to be picking up the right version.  anyway, I've nuked all the other jboss cache jars out of our app srever & ear.

>From our persistence.xml:

  | <property name="hibernate.cache.provider_class" value="org.hibernate.cache.TreeCacheProvider"/>
  | 

Our cache config:

  | <?xml version="1.0" encoding="UTF-8" ?>
  | <server>
  |   <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" />
  | 
  |   <!--  ====================================================================  -->
  |   <!--  Defines TreeCache configuration                                       -->
  |   <!--  ====================================================================  -->
  |   <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=SpurwingTreeCache">
  |     <depends>jboss:service=Naming</depends>
  |     <depends>jboss:service=TransactionManager</depends>
  | 
  | 
  |     <!-- Configure the TransactionManager -->
  |     <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
  | 
  | 	<!-- 
  | 			Node locking scheme : 
  | 								PESSIMISTIC (default)
  | 								OPTIMISTIC 
  | 	-->
  | 	<attribute name="NodeLockingScheme">PESSIMISTIC</attribute>		
  | 
  |     <!--
  |             Node locking isolation level : 
  | 								 SERIALIZABLE
  |                                  REPEATABLE_READ (default)
  |                                  READ_COMMITTED
  |                                  READ_UNCOMMITTED
  |                                  NONE
  | 
  | 			(ignored if NodeLockingScheme is OPTIMISTIC)
  |     -->
  |     <attribute name="IsolationLevel">READ_COMMITTED</attribute>
  | 
  |     <!-- Lock parent before doing node additions/removes -->
  |     <attribute name="LockParentForChildInsertRemove">true</attribute>
  | 
  |     <!--     Valid modes are LOCAL
  |                              REPL_ASYNC
  |                              REPL_SYNC
  |                              INVALIDATION_ASYNC
  |                              INVALIDATION_SYNC
  |     -->
  |     <attribute name="CacheMode">LOCAL</attribute>
  |     
  |     <!--  Whether each interceptor should have an mbean
  |         registered to capture and display its statistics.  -->
  |     <attribute name="UseInterceptorMbeans">true</attribute>
  | 
  |     <!-- Name of cluster. Needs to be the same for all TreeCache nodes in a
  |     cluster, in order to find each other -->
  |     <attribute name="ClusterName">Spurwing-PojoCache-Cluster</attribute>
  | 
  |     <!-- Uncomment next three statements to enable JGroups multiplexer.
  |          This configuration is dependent on the JGroups multiplexer being
  |          registered in an MBean server such as JBossAS. -->
  |     <!--
  |     <depends>jgroups.mux:name=Multiplexer</depends>
  |     <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
  |     <attribute name="MultiplexerStack">udp</attribute>
  |     -->
  | 
  |     <!-- JGroups protocol stack properties. ClusterConfig isn't used if the
  |      multiplexer is enabled and successfully initialized. -->
  | <!--     <attribute name="ClusterConfig">
  |       <config> -->
  |         <!-- 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_port="45566" 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" max_xmit_size="8192" retransmit_timeout="600,1200,2400,4800" up_thread="false"
  |            down_thread="false" />
  |         <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" down_thread="false" />
  |         <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" 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" />
  |       </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">5000</attribute>
  |     
  |     <!--    Number of milliseconds to wait until all responses for a
  |             synchronous call have been received.
  |     -->
  |     <attribute name="SyncReplTimeout">10000</attribute>
  | 
  |     <!--  Max number of milliseconds to wait for a lock acquisition -->
  |     <attribute name="LockAcquisitionTimeout">15000</attribute>
  | 
  |     <!--  Name of the eviction policy class. -->
  |     <attribute name="EvictionPolicyClass">org.jboss.cache.aop.eviction.AopLRUPolicy</attribute>
  | 
  |     <!--  Specific eviction policy configurations. This is LRU -->
  |     <attribute name="EvictionPolicyConfig">
  |       <config>
  |         <attribute name="wakeUpIntervalSeconds">5</attribute>
  |         <!--  Cache wide default -->
  |         <region name="/_default_">
  |          <attribute name="maxNodes">5000</attribute>
  |          <attribute name="timeToLiveSeconds">1000</attribute>
  |          <!-- Maximum time an object is kept in cache regardless of idle time -->
  |          <attribute name="maxAgeSeconds">120</attribute>
  |        </region>
  | 
  | 	   <region name="forgotPasswordRequest">
  | 		   	<attribute name="maxNodes">1000</attribute>
  | 		   	<attribute name="maxAgeSeconds">3600</attribute>
  | 		   	<attribute name="timeToLiveSeconds">0</attribute>
  | 	   </region>
  | 	   
  | 	   <region name="ReconciliationOrgCodeLookup">
  | 		   	<attribute name="maxNodes">1000</attribute>
  | 		   	<attribute name="maxAgeSeconds">3600</attribute>
  | 		   	<attribute name="timeToLiveSeconds">0</attribute>
  | 	   </region>       
  | 
  | 	   <region name="ReservationStatusQuery">
  | 		   	<attribute name="maxNodes">1000</attribute>
  | 		   	<attribute name="maxAgeSeconds">3600</attribute>
  | 		   	<attribute name="timeToLiveSeconds">0</attribute>
  | 	   </region>   
  | 	   
  | 	   <region name="getModuleByName">
  |     		<attribute name="maxNodes">15</attribute>
  |     		<attribute name="maxAgeSeconds">3600</attribute>
  |     		<attribute name="timeToLiveSeconds">0</attribute>
  | 		</region>    
  | 		
  | 		<region name="getTransactionByName">
  |     		<attribute name="maxNodes">15</attribute>
  |     		<attribute name="maxAgeSeconds">3600</attribute>
  |     		<attribute name="timeToLiveSeconds">0</attribute>
  | 		</region>         
  | 
  |       </config>
  |     </attribute>
  | 
  |   </mbean>
  | </server>     
  | 



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

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



More information about the jboss-user mailing list