For some reason the log4j output always defaults to DEBUG and to the console the first time Turbine 2.3 starts up. If I "reload" the app, it uses the defaults in the log4j.properties file correctly. What's interesting is, the first time over (when it outputs all the DEBUG info to the console), it does actually mention that it is reading the log4j.properties file. I used the log4j.properties file as it comes in the 2.3 CVS, and have also played around with it a bunch... Any ideas? Thanks, Brad
- RE: log4j DEBUG output at Turbine 2.3 startup Folkens, Brad
- RE: log4j DEBUG output at Turbine 2.3 startup David Wynter
- RE: log4j DEBUG output at Turbine 2.3 startup Folkens, Brad
- RE: log4j DEBUG output at Turbine 2.3 startup David Wynter
- RE: log4j DEBUG output at Turbine 2.3 startup David Wynter
- RE: log4j DEBUG output at Turbine 2.3 startup Folkens, Brad
- RE: log4j DEBUG output at Turbine 2.3 startup David Wynter
- RE: log4j DEBUG output at Turbine 2.3 startup Eric Pugh
- RE: log4j DEBUG output at Turbine 2.3 startup Folkens, Brad
- RE: log4j DEBUG output at Turbine 2.3 startup Folkens, Brad
