View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820413#3820413
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820413 Hi, I'd like to do parts of this. Although it can be solved by writing specific MBeans, I was thinking of a more generic mechanism that will monitor JMX notification and through the execution of BeanShell scripts will decide what is an alarm and what is not, so as to be able to monitor any aspect of a deployment, not just memory and CPU. All come back with a more concrete proposal. Regards /Dimitris Andreadis ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
