"scott.stark(a)jboss.org" wrote : Background events are not something we want on the console(INFO). Just filtering them out is not something we want to do either as then even the server.log (which defaults to DEBUG level) would not have this info. Generally such background processing is a TRACE level event in terms of the jbossas levels. We could live with DEBUG though. | I'll take a look and see what the easiest solution is short-term. anonymous wrote : | Differing views on logging levels is the bane of all logging frameworks. In the absence of mechanism to map a given (category,level) pair onto a (category,jbossas-level) I don't know how to reconcile this. Can we create a org.jboss.logging.LoggerPlugin that bridges between the arjuna logging framework and the jbossas framework? | We probably already have that capability. We don't access the logger implementation directly, but go through a plugin framework. It may be possible to have a plugin specifically for AS that does the mapping transparently to TS. That may even be the easiest short-term solution! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983084#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...