Is it just the jars or do you even have a logging configuration file (like log4j.xml or log4j.properties or logging.properties) within that application? It does look like the presence of these logging libraries might be causing this (sigh!).
By the way, just a note - in production logging to console isn't really a good idea. So even if you end up fixing the issue, you might still want to just keep logging to log files instead of the console.
Joined: Jun 15, 2006
we are using log4j.properties to store error logs into the file. A part from that System.out.println are also used for initial level of debugging.