Is that directory on the classpath somewhere higher than the weblogic app classloader? For example is it on the system classpath or server classpath?
Where is the class which triggers log4j initialization? Is it contain within the war file? If, for example, and ejb component is the first to reference log4j, it would not be able to see the stuff in the WEB-INF/classes directory. What else is inside the ear file? Is everything in the ear supposed to share that log4j config? -----Original Message----- From: Crumbo, Brian [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2003 12:48 PM To: '[EMAIL PROTECTED]' Subject: Picking up wrong properties file in Weblogic I have deployed an application as an ear file to Weblogic. The war file within the ear file contains the log4j.properties file in the WEB-INF/classes directory, and the log4j.jar in the WEB-INF/lib directory. My understanding is that log4j should pick up the log4j.properties file from the WEB-INF/classes directory by default. However, my application, for some unknown reason, is picking up a log4j.properties file from elsewhere on my machine...from a directory that contains a Java application that has not been deployed. Anybody know why log4j would be going outside the web app to pick up another properties file? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
