Home/ Questions/Q 6873139
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T04:01:17+00:00

I finally got log4j setup with spring mvc, my log4j properties looks like: #

  • 0

I finally got log4j setup with spring mvc, my log4j properties looks like:

# Direct log messages to stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L - %m%n

# Root logger option
log4j.rootLogger=trace, stdout

Now I don’t want to see any output except from my own code, is there a way to restrict all log messages to a specific namespace?

When I go into production, I don’t want any trace/debug information logged, I guess I have to create a file appender but how would I go about restricting the log messages to only severe type log messages like in a try/catch or something unexpected?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For example (using a ConsoleAppeneder, but same difference):

    log4j.rootLogger=INFO, A1
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.your.package.to.debug=DEBUG
log4j.logger.org.springframework.aop=DEBUG

    This logs at the INFO level by default, except for the your.package.to.debug and spring-aop packages, logged at the DEBUG level. Mix and match levels and packages however required.

    I’d be wary of not putting INFO into production unless you never need to debug anything, though–particularly during startup, INFO is really important. It can also be used to provide general system information.

    Also, the %L pattern is pretty slow. Fine for rare WARNING/etc. logs, not so much for normal operational logging.

    • 0