LoggingMonitor mbean dependencies

[mtihepner]

I'm running JBOSS 3.2.7 and I've added the LoggingMonitor jar.
I'm currently getting this error message during bootup:


2006-04-13 20:27:28,275 WARN [org.jboss.services.loggingmonitor.LoggingMonitor] Unable to log attributes for mbean: jboss.web:type=ThreadPool,name=jk-8009
javax.management.InstanceNotFoundException: jboss.web:type=ThreadPool,name=jk-8009 is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:454)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:433)
at org.jboss.services.loggingmonitor.MonitoredMBean.logAttributes(MonitoredMBean.java:101)
at org.jboss.services.loggingmonitor.LoggingMonitorTimerTask.run(LoggingMonitorTimerTask.java:54)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)


I realize this is because the LoggingMonitor mbean starts before the mbean that I'm trying to monitor. I think need to setup a dependency in the LoggingMonitor mbean but this doesn't work for "jboss.web:type=ThreadPool,name=jk-8009" because it is not a service mbean.
So...
Is there a way I can set the LoggingMonitor to load last?
Is there something that loads at the end of the boot process that I can make it depend on?

Any help would be appreciated.
thanks,
Tim

[jiwils]

"mtihepner" wrote:
Is there a way I can set the LoggingMonitor to load last?

In your server configuration's deploy directory, add a deploy.last directory and place your LoggingMonitor MBean descriptor in that directory. Then, it will get deployed last, but since the MBean you are monitoring deals with Tomcat's connectors (which get loaded after JBoss "starts"), I am not sure this will work.

[jiwils]

I should have added that this issue is solved by the JBoss Barrier Controller service in JBoss 3.2.8+/4.0.2+, which was written to solve problems just like this.

[mtihepner]

Adding my LoggingMonitor MBean descriptor into a deploy.last directory delayed the warning on "jboss.web:type=ThreadPool,name=jk-8009" but it didn't prevent them. I was having the same issue other mbeans and this did resolve those problems.

If this is problem resolved in later version of jboss I can control the warnings with log4j and wait until we can upgrade.

thanks for your fast response.
-tim