This problem is driving me crazy because I am not sure why this just started happening, and I have already wasted a week on it with absolutely no progress.
I am maintaining a legacy application running on JBoss 4.3 utilizing:
The log files have always been polluted with (what I am guessing is Apache?) garbage like:
07:37:04,024 DEBUG [Digester] New match='web-app/mime-mapping/extension'
07:37:04,024 DEBUG [Digester] Fire begin() for CallParamRule[paramIndex=0, attributeName=null, from stack=false]
07:37:04,024 DEBUG [sax] characters(tcl)
07:37:04,028 DEBUG [sax] endElement(,,extension)
07:37:04,028 DEBUG [Digester] match='web-app/mime-mapping/extension'
07:37:04,028 DEBUG [Digester] bodyText='tcl'
07:37:04,028 DEBUG [Digester] Fire body() for CallParamRule[paramIndex=0, attributeName=null, from stack=false]
07:37:04,028 DEBUG [Digester] Popping body text
I never really cared until recently when the following line has been followed by hundreds of thousands of lines of whitespace.
07:37:04,024 DEBUG [Digester] Pushing body text '
...
'
Now I care greatly because for auditing reasons we must maintain these log files indefinitely and they start out after server restart at around 20MB.
I initially figured that by disabling Sax Digester logging from log4j.properties that I solved the problem but nothing I have attempted has been working.
http://programming.itags.org/development-tools/59562/
https://community.jboss.org/thread/4401
http://www.coderanch.com/t/47763/Struts/disable-struts-debug-info-messages
http://mail-archives.apache.org/mod_mbox/logging-log4j-user/200210.mbox/%[email protected]%3E
http://deepaksrivastav.com/?p=63
http://www.mail-archive.com/[email protected]/msg10703.html
Somebody here mentioned that their could be the possibility of a rogue log4j.properties or simplelog.properties floating around on the classpath that is causing me this grief but after an exhaustive witch hunt I find nothing is truly supressing the log file pollution.
Any help or advice would be greatly appreciated.
EDIT: A great suggestion below reminded me that I had already tried setting logging to WARN on everything within the JBoss log4j xml configuration file for this server instance. Literally nothing changed. I noticed that the temp files and working directories were not getting cleaned up properly too so I wiped them and still nothing. Hope this information helps and not scare away people thinking, "Man, that guy is screwed!" :)
Turn off debug logging in server/xxx/conf/jboss-log4j.xml. Set it to info so that you will not see all these unnecessary logging lines