In the current version of EJB3 on JBoss-5.0GA, a bean method invocation always generates a lot of these WARN messages: WARN [InterceptorRegistry] applicable interceptors is non-existent for ..... Looking at the InterceptorRegistry, i do see a TODO with some explanation: | public List<Class<?>> getApplicableInterceptorClasses(Method method) | { | List<Class<?>> methodApplicableInterceptorClasses = applicableInterceptorClasses.get(method); | //TODO | //FIXME: This assertion is valid, but EJB3 Core needs to declare virtual methods without interceptors | // such that they make the Map of MethodHashes, and these then get improperly placed in the | // Joinpoint Map, which ends up here... | //assert methodApplicableInterceptorClasses != null : "applicable interceptors is non-existent for " + method; | log.warn("applicable interceptors is non-existent for " + method); | ... | } 1) Could we reduce the logging level to maybe DEBUG, since this message is not really for the end-user. 2) Is that logging message missing a if block? The earlier assert statement (which now is commented out) was checking whether the methodApplicableInterceptorClasses is null. The log message does not do this. Or is it that the methodApplicableInterceptorClasses is always null? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199701#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...