4.2.3 still has DEBUG messages in boot.log on first start up.
Howdy. So, a pretty weird issue here, but when I first install my app to Jboss 4.2.3, during which the installer extracts the log4j.properties in run.jar and replaces it with the following, the very first time I start the server I still get DEBUG messages. The file only goes to 74Kb, so it's not anything insane, and I can restart the service (we run with wrapper-3.5.6) over and over and no more DEBUG messages.
Here's the props file:
### ====================================================================== ###
## ##
## JBoss Bootstrap Log4j Configuration ##
## ##
### ====================================================================== ###
### $Id: log4j.properties 41281 2006-02-18 00:05:17Z starksm $ ###
log4j.rootCategory=INFO, FILE, CONSOLE
### A bootstrap file appender
log4j.appender.FILE=org.jboss.logging.appender.DailyRollingFileAppender
log4j.appender.FILE.File=${jboss.server.log.dir}/boot.log
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.DatePattern='.'yyyy-MM-dd
log4j.appender.FILE.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n
log4j.appender.FILE.Append=true
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=INFO
log4j.appender.CONSOLE.Target=System.out
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n
So we're not doing anything abnormal, I would think. I just can't figure out why initially there are debug messages. If I reinstall over top the current install, and start the service, no debug messages will appear, either. It's just on that first install when Jboss is in a "clean" state.
Has anyone seen this issue, or know where I can look to turn those debug messages off?
Thanks!
Jason
EDIT: Actually, each time I reinstall my app and restart the service after that install (part of which removes the tmp directory), I get a 74kb boot.log file with DEBUG in it.