Log4j suddenly stops logging

Question

I\'m build a Portlet application deployed to a WebSphere Portal Server running on Linux. Every Portlet WAR uses Log4j for logging with a configuration like this, having ever

Answer 1

For over 5 years, Log4j has hardly any bugs fixed: it's effectively a dead project. If acceptable, consider replacing it with Logback, which implements SLF4j directly.

Logback and SLF4J are written by the same guy who wrote Log4J (Ceki), has an even more liberal license and has a good community. It is the successor to Log4J 1 in every way possible (except for its name).