Thursday, February 19, 2004 12:33 PM
Our team faced the same difficulty using log4j on our WAS 4 server (AIX). After searching around I ended up reading the article:
We made sure that the log4j-1-2-8.jar file was in the $WAS_HOME/lib/app directory as well as in the module classpaths. I switched the "Module Visibility" of the application server from "Module" to "Server" and now log4j operates properly.
Hope this helps...