That makes perfect sense. You need to satisfy three conditions to get this warning: 1) No log4j.properties or log5j.xml file 2) The lag4j.jar file in your classpath 3) Invoke a method that tried to log something Apparently, when your client calls an EJB, all three conditions are satisfied. For other clients, one or more of these conditions is not satisfied (probably not methods are doing logging). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082443#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...