"ramone1234" wrote : Do you have any idea why this is happening? The short answer is that the logging monitor service is being deployed before JBossWeb (Tomcat), so the MBean you wish to monitor is not yet available. The errors you see go away (and everything works like you wish) once the MBean you are monitoring becomes available.
For many uses of logging monitor, you can resolve this issue by using the MBean depends tag in the logging monitor XML descriptor to cause the deployment of logging monitor to depend on the deployment of the MBean you are monitoring. See the provided example for monitoring the default datasource on the wiki page for an illustration on how to do this ( http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossLoggingMonitorExampleDefaultDSServiceConfig ). In your case, however, the MBean that you are using can not be depended on in this manner. See http://wiki.jboss.org/wiki/Wiki.jsp?page=MyDependencyDoesntWork for more information. By adding the dependency specified below to your logging monitor deployment descriptor, you can make the logging monitor deployment depend upon the deployment of the web server service, and that causes the logging monitor deployment to wait until the web server service (and the MBean you wish to monitor) becomes available. <depends>jboss.web:service=WebServer</depends> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890294#3890294 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890294 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
