[jboss-user] [JBoss Cache: Core Edition] - Re: ObjectName with invalid character

setatum do-not-reply at jboss.com
Thu Feb 12 15:13:05 EST 2009


I've noticed the same problem. I'm running JBC 3.0.0-GA under WebLogic 9.2, Sun JDK 1.5.0_10.

What I've found is that this only happens when I set CacheMode to LOCAL. If I use REPL_SYNC or REPL_ASYNC, then it starts up fine. 

Below is my config file, FWIW:


  | <?xml version="1.0" encoding="UTF-8" ?>
  | 
  | <server>
  |    <mbean code="org.jboss.cache.pojo.jmx.PojoCacheJmxWrapper" 
  |           name="jboss.cache:service=PojoCache">
  |       
  |       <depends>jboss:service=TransactionManager</depends>
  | 
  |       <!-- Configure the TransactionManager -->
  |       <attribute name="TransactionManagerLookupClass">
  |          <!-- org.jboss.cache.transaction.DummyTransactionManagerLookup -->
  |         org.jboss.cache.transaction.JBossTransactionManagerLookup
  |       </attribute>
  | 
  |       <!-- Isolation level : SERIALIZABLE
  |                              REPEATABLE_READ (default)
  |                              READ_COMMITTED
  |                              READ_UNCOMMITTED
  |                              NONE
  |       -->
  |       <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
  | 
  |       <!-- Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC -->
  |       <!-- LOCAL causes the ":" error, REPL_* does not. -->
  |       <attribute name="CacheMode">LOCAL</attribute>
  | 
  |       <!-- Name of cluster. Needs to be the same for all caches, 
  |            in order for them to find each other
  |       -->
  |       <attribute name="ClusterName">dev-mwDevCluster</attribute>
  | 
  |           <!-- JGroups protocol stack properties. -->
  |       <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_addr="228.1.2.3" mcast_port="48866"
  |                  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"/>
  |             <MERGE2 min_interval="10000" max_interval="20000"/>
  |             <FD shun="true"/>
  |             <FD_SOCK/>
  |             <VERIFY_SUSPECT timeout="1500"/>
  |             <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
  |                            max_xmit_size="8192"/>
  |             <UNICAST timeout="600,1200,2400,4800"/>
  |             <pbcast.STABLE desired_avg_gossip="400000"/>
  |             <FC max_credits="2000000" min_threshold="0.10"/>
  |             <FRAG2 frag_size="8192"/>
  |             <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
  |                         shun="true" print_local_addr="true"/>
  |             <pbcast.STATE_TRANSFER/>
  |          </config>
  |       </attribute>
  | 
  |       <!-- Whether or not to fetch state on joining a cluster -->
  |       <attribute name="FetchInMemoryState">true</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">15000</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>
  |    
  |    </mbean>
  | </server>
  | 
  | 

It would be nice to set LOCAL mode on the single server setups I have, so any info on this would be appreciated. Hope this helps.

-Scott

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

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



More information about the jboss-user mailing list