Yes i use async,
i don't use flow control protocol (i don't now if it's supported in this
release of JBoss (1.2.4/jgroups 2.2.8),
but as you can see in my publisher test class, all 1000 msg (via modulo)
i call a sleep of 2000ms (i have test without).
What is very strange is, this is not the publisher but the sender which grow up
in memory.
more strange and more supect for a production release is that the memory never
retrieve a normal space.
( i mean: ok the JVM has allocate a big space of memory to compute a burst of
msg, but when all msg have been send by the publisher
(for example i test with 100 000 msg) the memory stay at the same level (and a
force gc has no impact).
Today, i try to test with TreeCache aonly (without AOP features).
Christophe
?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
|
| dependsjboss:service=Naming/depends
| dependsjboss:service=TransactionManager/depends
|
| !--
| Configure the TransactionManager
| --
| attribute
name=TransactionManagerLookupClassorg.jboss.cache.DummyTransactionManagerLookup/attribute
|
| !--
| Isolation level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| --
| attribute name=IsolationLevelREPEATABLE_READ/attribute
|
| !--
| Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC
| --
| attribute name=CacheModeREPL_ASYNC/attribute
|
| !--
| Just used for async repl: use a replication queue
| --
| attribute name=UseReplQueuefalse/attribute
|
| !--
| Replication interval for replication queue (in ms)
| --
| attribute name=ReplQueueInterval0/attribute
|
| !--
| Max number of elements which trigger replication
| --
| attribute name=ReplQueueMaxElements0/attribute
|
| !-- Name of cluster. Needs to be the same for all clusters, in
order
| to find each other
| --
| attribute name=ClusterName**TEST**/attribute
|
| !-- JGroups protocol stack properties. Can also be a URL,
| e.g. file:/home/bela/default.xml
| attribute name=ClusterProperties/attribute
| --
|
| attribute name=ClusterConfig
| config
| UDP mcast_send_buf_size=1000
mcast_port=6667 ucast_recv_buf_size=1000
| mcast_addr=239.255.8.15
bind_to_all_interfaces=true loopback=false mcast_recv_buf_size=1000
| max_bundle_size=64000
max_bundle_timeout=30 use_incoming_packet_handler=false
| use_outgoing_packet_handler=true
ucast_send_buf_size=1000 ip_ttl=32 enable_bundling=true /
| PING timeout=2000 down_thread=false
num_initial_members=3 /
| MERGE2 max_interval=1
down_thread=false min_interval=5000 /
| FD_SOCK down_thread=false /
| VERIFY_SUSPECT timeout=1500
down_thread=false /
| pbcast.NAKACK max_xmit_size=6
down_thread=false use_mcast_xmit=true gc_lag=50
|
retransmit_timeout=300,600,1200,2400,4800 discard_delivered_msgs=true/
| UNICAST timeout=300,600,1200,2400,3600
down_thread=false /
| pbcast.STABLE stability_delay=1000
desired_avg_gossip=5000 down_thread=false max_bytes=25 /
| pbcast.GMS print_local_addr=true
join_timeout=3000
