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.
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.
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.