Programmatically: 1) You'll need somesort of threshold that would define when to flush the cache 2) When that threshold is reached, use the JMX calls to flush the cache.
If you want to automate it, you could schedule a job or start your own MBean Service(a worker thread) that periodically checks the threshold. For simplicity, develop a tool that uses the JMX layer to flush the cache. Depending on your expected response time to flush the cache, you may want to do it. On-Demand(mid tx) Soon(post to a MDB) Convenience(background schedule thread) For a large application, creating a backdoor with a special "Flush current state" may be a good idea. In that fashion, you can change your current configuration in many places without affecting the current running system. Then when everything is set/ready, you can push the "magic button" and the configuration becomes part of the application. I use to do this for online trading services to reroute trades without disrupting our live clients. It was seamless and effective. Good luck, -Ivan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846336#3846336 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3846336 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
