[jboss-user] [JBossCache] - JBoss Tree Cache Eviction Plicy Configuration

[dsualeh]

Hi ,
I am using the LRU Eviction Policy for my JBoss Tree Cache running REPL_ASYNC 
mode.
My desired result is that the when the cache is filled up with 20 modes, it 
should remove the old nodes in least recently used fashion to accomodate new 
ones
 
I would like to know what is the exact significance of the Time to Live 
Seconds  parameter?

The doc say is the idle time before a node is swept away and 0 denotes no 
limit. 
Can above offer more detail on this ?

Thanks in advance,
Danish 







View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4050087#4050087

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050087
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBossCache] - Help need in delplying JBoss Cache as a distributed cache

[dsualeh]

Hi guys.
I am having troubling in deploying JBoss as a distributed cache.
Can someone please have a look at my property configuration
Your help will be very much appreciated

?xml version=1.0 encoding=UTF-8?

!-- = --
!--
--
!--  Sample TreeCache Service Configuration
--
!--
 --
!-- = --






!--  
--
!-- Defines TreeCache configuration
   --
!--  
--



jboss:service=Naming

jboss:service=TransactionManager


!--
Configure the TransactionManager
--
!--
org.jboss.cache.DummyTransactionManagerLookup
--


!--
Isolation level : SERIALIZABLE
  REPEATABLE_READ (default)
  READ_COMMITTED
  READ_UNCOMMITTED
  NONE
--

NONE


!--
 Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC
--
REPL_ASYNC

!--
Just used for async repl: use a replication queue
--
false

!--
Replication interval for replication queue (in ms)
--
0

!--
Max number of elements which trigger replication
--
0

!-- Name of cluster. Needs to be the same for all clusters, in order
 to find each other
--
GlueCache-GD

!-- JGroups protocol stack properties. Can also be a URL,
 e.g. file:/home/bela/default.xml
   
--



!-- UDP: if you have a multihomed machine,
set the bind_addr attribute to the appropriate NIC IP address, 
e.g bind_addr=192.168.0.2
--
!-- 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=15 mcast_recv_buf_size=8
ucast_send_buf_size=15 ucast_recv_buf_size=8
loopback=true/
PING timeout=2000 num_initial_members=3
up_thread=false down_thread=false/
MERGE2 min_interval=1 max_interval=2/
!--FD shun=true up_thread=true down_thread=true 
/--
FD_SOCK/
VERIFY_SUSPECT timeout=1500
up_thread=false down_thread=false/
pbcast.NAKACK gc_lag=50 
retransmit_timeout=600,1200,2400,4800
max_xmit_size=8192 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=2
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=true down_thread=true/




!--
Whether or not to fetch state on joining a cluster
   --
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
--
12

!--
Number of milliseconds to wait until all responses for a
synchronous call have been received.
--
1

!-- Max number of milliseconds to wait for a lock acquisition --
25000


!-- Name of the eviction policy class. --
 

org.jboss.cache.eviction.LRUPolicy  


600

1
0













   !--  Uncomment to get