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
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937283#3937283
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3937283
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
