Log4j ignores fileappender, writes to SystemOut

[Darien Cheung]

Hi,

I have a problem with Log4j using Websphere 6.0. My module is configured with a properties file and all the logs were being sent to the appropriate file appender. Then something in our software changed and the logs are now being sent to SystemOut. As far as I can tell, nothing in the configuration has changed (i.e. file appender is still there, log4j still parses it on startup..). Under what circumstances would something like this happen? Does this behaviour mean that my appender is no longer in memory? (any way I can check at runtime?) I'm at wits end trying to debug this issue!

Thanks very much

[Jaikiran Pai]

Can you post the contents of your log4j file? Also where in your application, do you place this file? Do you have any code that explicitly loads the log4j configuration file? If yes, please post the same.

[Paul Michael]

Would you know if your application uses Commons Logging as a logging abstraction?

In that case the configuration for Commons logging might have changed to use JDK logging instead of Log4J.