-
as seen on Stack Overflow
- Search for 'Stack Overflow'
This is the log4j.properties that i have in my app
log4j.rootLogger=B C
log4j.logger.A=INFO, A1
log4j.debug=false
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %C - %m%n
log4j.logger…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Here is my current log4j settings file. Are these settings ideal for production use or is there something I should remove/tweak or change? I ask because I was getting all my threads being hung due to log4j blocking. I checked my open file descriptors I was only using 113.
# ***** Set root logger…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I'm having troubles understanding the relation between additivity, category logging level and appender threshold...
here's the scenario (my log4j.properties file):
log4j.category.GeneralPurpose.classTypes=INFO, webAppLogger
log4j.additivity.GeneralPurpose.classTypes=true
log4j.category.GeneralPurpose=ERROR…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
The following is a basic log4j configuration inside Config.groovy using the log4j DSL with Grails 1.2, it works as expected (log all errors to the given file):
log4j = {
appenders {
file name:'file', file:"c:/error.log"
}
error 'grails.app'
root {
error 'file'
…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hello,
I've got log4j configured on my Java project with the following log4j.properties:
log4j.rootLogger=WARNING, X
log4j.appender.X=org.apache.log4j.ConsoleAppender
log4j.appender.X.layout=org.apache.log4j.PatternLayout
log4j.appender.X.layout.ConversionPattern=%p %m %n
log4j.logger.org.hibernate…
>>> More
