I had experienced a similar problem with lots of [aop-trace] output running a client code against JBoss server The problem has gone away, when jboss-logging-log4j.jar was placed in client CLASSPATH. Apparently, default logging is done by org.jboss.logging.Log4jLoggerPlugin, which was missing from classpath, and SystemOutLoggerPlugin was used instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200421#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...