This is a bug http://jira.jboss.com/jira/browse/JBAOP-584 Currently, our tests don't reproduce this error because, at the moment of deployment, there are no advisors active. In your case, it seems that there are advisors enabled during the moment the aspect is deployed (i.e., there are instrumented classes that have already been loaded at the moment). This uncovered the bug. I don't think there will be time enough to fix this bug before we go GA. But, after that, I will try to fix it asap. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154437#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...