JES5 and log4j inconsistencies from 2005Q4 with multiple web applications
We recently upgraded from JES 2005Q4 to JES5, and did a fresh installation of Solaris 9 & JES5. All our servlets and portlets in the portal server seem to work ok with the exception of our log4j logging mechanism.
We have 4 customized portlets and 5 servlets, and are using the same instance on the Application Server as the host for our access manager, portal server, and custom servlets & portlets.
On 2005Q4, we had each of our portlets and servlets logging to separate log files using log4j (v1.2.8), by placing the log4j jar file in each web app's WEB-INF/lib path, with the log4j.properties file in each web app's WEB-INF/classes path, and it was working fine logging to separate log files for each web application.
But when I deploy the same servlets and portlets to JES5, whichever application happens to have written a log entry first appears to create/log to it's respective log file. Unfortunately, all our other servlets and portlets also then using the same log file, apparently using the same properties file as the first one that logged, even though the settings for each call out separate log files.
I've googled extensively to see if we're doing something wrong, but am fairly certain we are doing everything correctly since we have placed the log4j jar file in each web app's warfile. Does anyone know what's different between 2005Q4 & JES5 that may be causing this? Is this a class loader issue? I've checked the App Server JVM classpath and it does not include log4j's jar file. The portal server and psconsole apps have it defined in their respective WEB-INF/lib paths, but that shouldn't (and isn't) interfering with our apps' use of log4j.
Any help is greatly appreciated. Thanks in advance!
