"prpo" wrote : | a) Just package the shared library with the ejb - no overriding of java2ParentDelegation - Does not locate the log4j.xml | | Any insights? | In this scenario, where exactly is the log4j.xml placed? Is it inside the shared.jar or inside the ejb.jar? When you say you are packaging the shared jar with the ejb jar, how exactly are you doing this? Packaging one jar inside other? I think the reason why the log4j.xml is not being picked up is because of the singleton nature of the log4j Logger class. Unless a new instance of the Logger object is not created through the application specific classloader, the log4j properties/xml file initialization will not happen. Furthermore, add the -log4j:debug parameter to the JAVA_OPTS in your run.bat of JBoss. This parameter will printout to the STDOUT (console) internal log4j messages which will help you understand where log4j is looking for the file. Also, is the shared library code part of your applicaiton? And do you have rights to change the code (thinking of a last resort option). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185470#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...