Even though the Logger level is set to ALL, the ConsoleHandler (the default Handler on the logger) still has a default level of INFO. This comes from the default logging.properties in JAVA_HOME/jre/lib
More Related Contents:
- Spring Boot – How to log all requests and responses with exceptions in single place?
- How to Create a Custom Appender in log4j2?
- Setting a log file name to include current date in Log4j
- Configuring Log4j Loggers Programmatically
- How to set up java logging using a properties file? (java.util.logging)
- Is it worth to use slf4j with log4j2
- How to enable wire logging for a java HttpURLConnection traffic?
- How to send java.util.logging to log4j?
- Why not use java.util.logging?
- Log4j: How to configure simplest possible file logging?
- How to change root logging level programmatically for logback
- NullPointerException stack trace not available without debug agent
- Logging while testing through Gradle
- Why are the Level.FINE logging messages not showing?
- How to configure log4j to log different log levels to different files for the same logger
- How do I get java logging output to appear on a single line?
- How to customize log4j2 RollingFileAppender?
- Are there technical reasons to prefer using logback instead of log4j?
- Where do I configure log4j in a JUnit test class?
- Rolling logback logs on filesize and time
- How to specify Log4J 2.x config location?
- Configuring RollingFileAppender in log4j
- Configuring log4j2 and log4j using a single log4j2 xml file
- How to log within shutdown hooks with Log4j2?
- How to log all active properties of a spring boot application before the beans instantiation?
- Enable logging in Apache Commons Net for FTP protocol
- When to log a stacktrace for a caught exception
- What is the issue with the runtime discovery algorithm of Apache Commons Logging
- How to create different log files for different packages using same log4j logger?
- Log4j2 (2.1) custom plugin not detected by packages attribute