The JBossTS code sets its own logger because we have a custom implementation that supports internationalization. As far as I can tell the problem is that all the other AS code expects the log factory to have the default configuration, so is not setting it explicitly. Thus if it runs after the JBossTS code has modified the factory configuration it is getting unexpected results. One simple (although not threadsafe) option may be for the JBossTS code to reset the original factory config when it is done instantiating its own loggers. I'm not clear why other code would be affected by the changing of log level for messages. That code is not part of the custom Log4JLogger, but rather done via a wrapper around it, so it should not get picked up except by the JBossTS logging system. Is there a test case that shows where this level changing is affecting other pats of the AS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126096#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...