The log4j exception is unrelated, but you should fix this anyhow. The error message you mention is benign. Basically, when we have pointcuts for fields and constructors we need to change the code calling those fields/constructors so that the woven code executing the aspects is called. So when weaving a class we find all the classes it acceses, and try to load up each of those classes in the weaver to see if their fields/constructors match any pointcuts. So basically the messages mean that StandarServer and ServerContext reference NamingContextListener and NamingContextListener is not on the classpath. THis is not really a problem since the code calling NamingContextListener is not called (or when running tomcat you'd get ClassNotFoundExceptions) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958830#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...