"ivelin" wrote : | ... | 1) Scheduling based CPU estimate. Schedule a regular heartbeat task which will measure the time between two runs. If the delay is over the scheduled interval for a prolonged (configurable) time, then broadcast JMX notification. | | 2) Memory monitor. A similarly scheduled task which measures the available memory and if it aproaches a certain limit, will send a Warning JMX Notification. If it reaches a critical limit, it will send an Alarm notification. The latter will probably cause the kernel to redeploy all modules. | ... |
I'm done with [2]: http://sourceforge.net/tracker/index.php?func=detail&aid=913422&group_id=22866&atid=381174 Ivelin, could you clarify a little bit [1]? If I understand periodically run and time the execution of a certain task. If it takes too long to execute (for a consequetive number of measurements) then broadcast a notification. What could make a suitable task? It could be configurable (e.g. execute a syncronous operation on some other MBean), still, what makes a good task? Regards /Dimitris <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825046#3825046";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825046>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
