mine is to enabled DEBUG on org.jboss.nukes and on the CMP layer to see the JDBC statements emitted by the CMP EJBs :
1/ look for the appender CONSOLE and move its Threshold param to DEBUG
2/ add org.jboss category with priority INFO
3/ add org.jboss.nukes with priority DEBUG
4/ add org.jboss.ejb.plugins.cmp with priority DEBUG
i've done that, but i end up getting some nasty debug output for what looks to be some kind of template.
the class name for these debug statements looks like this:
and turning the priority to INFO for org.jboss.nukes does not seem
to remove the output statements.
also, i notice for my debug statements, the category being used is the
mbean name, and not the class name. tracking back thru the code, i see that the mbean name (or the name i specify for a hot create) is what is passed to the AbstractMBean constructor.
i may be missing something, but doesn't' that create a whole seperate category that is completely seperate from the class name, thus forcing me to have to have a category in my log4j conf file that is specific for that insteance?
you should maybe set the category org.jboss.nukes.common
to priority INFO in that case.
yes these are the templates compiled by the template engine.
they are in debug logs so it should not be a pain
ok - i was a little confused by the console vs server.log output - and just noticed that the console output chops off most of the package name, so i'm now straight on that issue.
as for the template debug, the standard categories do not seem to work when it comes to turning off the output. i just tried this category, and it seems to have corrected the problem.
it seems as if the pattern won't be matched unless the "class" is prefixed to the package/class name string. after doing some hunting through the code, it seems that the method Object::getClass() prefixes the the actual class name w/ the string "class". (the getClass() method is invoked by the TemplateRepository class when requesting the logger).