Hello, we have done some more testing (using the standard UDP configuration). It seems like the memory problem is partly explained by a periodic PUT on the same key (and node) in the TreeCache. Every 1000 GETs we PUT a cache status object into the cache to let all other caches know the status of this TreeCache. We use the same node and the same key for one unique instance of a TreeCache (one per JVM). Somehow, this repeated PUT into the same node/key causes the cache to consume memory.
Question: if a PUT is repeatedly made on the same node/key in a replicated TreeCache, is it necessary to do a REMOVE on the same node/key before the PUT is made? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867039#3867039 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867039 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
