JBC 2.2.0 EvictionConfig not being recognized from configura
I have just started using Jboss Cache 2.2.0, I got it running with a quick experiment of distributed caching. I have simple needs, so far just strings shared in a cache between JVM's.
However, I run into problems when I add the EvictionConfig attribute to my cache config XML file. If I leave this attribute out the different JVMs start up and replicate objects. But I have no control over eviction.
Error I am seeing:
org.jboss.cache.config.ConfigurationException: Unknown configuration element EvictionConfig
Additionally, I have added other attributes like:
StateRetrievalTimeout">20000
20000
DEFAULT
true
But I see these errors in the trace output saying they are unrecognized:
2008-10-09 15:22:55,791 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute SyncReplTimeout. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute LockAcquisitionTimeout. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute StateRetrievalTimeout. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute wakeUpIntervalSeconds. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute policyClass. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute maxNodes. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute timeToLiveSeconds. Please check your configuration. Ignoring!!
2008-10-09 15:22:55,807 DEBUG org.jboss.cache.factories.XmlConfigurationParser [] - Unrecognised attribute LockParentForChildInsertRemove. Please check your configuration. Ignoring!!
Here is the config file in full. Any suggestions are much appreciated.
<?xml version="1.0" encoding="UTF-8"?>
<!-- =====================================================================
-->
<!-- -->
<!-- Sample JBoss Cache Service Configuration -->
<!-- -->
<!-- =====================================================================
-->
<!-- ====================================================================
-->
<!-- Defines JBoss Cache configuration -->
<!-- ====================================================================
-->
<!-- Note the value of the 'code' attribute has changed since JBC 1.x -->
<!-- Configure the TransactionManager -->
org.jboss.cache.transaction.GenericTransactionManagerLookup
<!-- Node locking level : SERIALIZABLE
REPEATABLE_READ (default)
Chapter 11. Configuration Ref...
108
READ_COMMITTED
READ_UNCOMMITTED
NONE -->
REPEATABLE_READ
<!-- Lock parent before doing node additions/removes -->
true
<!-- Valid modes are LOCAL (default)
REPL_ASYNC
REPL_SYNC
INVALIDATION_ASYNC
INVALIDATION_SYNC -->
REPL_SYNC
<!-- Name of cluster. Needs to be the same for all JBoss Cache nodes in a
cluster in order to find each other.
-->
JBossCache-Cluster
<!--Uncomment next three statements to use the JGroups multiplexer.
This configuration is dependent on the JGroups multiplexer being
registered in an MBean server such as JBossAS. This type of
dependency injection only works in the AS; outside it's up to
your code to inject a ChannelFactory if you want to use one.
-->
<!--
<depends optional-attribute-name="MultiplexerService"
proxy-type="attribute">jgroups.mux:name=Multiplexer
tcp
-->
<!-- JGroups protocol stack properties.
ClusterConfig isn't used if the multiplexer is enabled above.
-->
<!-- 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_SOCK/>
<VERIFY_SUSPECT timeout="1500"/>
<pbcast.NAKACK gc_lag="50" retransmit_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" shun="true" print_local_addr="true"/>
<pbcast.STATE_TRANSFER/>
<!--
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
-->
20000
<!--
Number of milliseconds to wait until all responses for a
synchronous call have been received.
-->
20000
<!-- Max number of milliseconds to wait for a lock acquisition -->
15000
<!-- Shutdown hook behavior. Valid choices are: DEFAULT, REGISTER and
DONT_REGISTER.
If this element is omitted, DEFAULT is used. -->
DEFAULT
<!-- Enables or disables lazy unmarshalling. If omitted, the default is that lazy unmarshalling
is enabled. -->
true
<!-- Specific eviction policy configurations. This is LRU -->
5
<!-- This defaults to 200000 if not specified -->
200000
org.jboss.cache.eviction.LRUPolicy
<!-- Cache wide default -->
5000
30
