Log4j2 properties | monitorInterval not working - java

I am using log4j 2.4 and trying to convert log4j2.xml to log4j.properties, however monitorInterval property doesn't seem to be working with log4j2.properties.
status = trace
name=PropertiesConfig
property.filename = logs
appenders = console, file
monitorInterval=10
though log4j2 following documentation
https://logging.apache.org/log4j/2.x/manual/configuration.html#Properties
clearly stats that
Properties configuration files support the advertiser,
monitorInterval, name, packages, shutdownHook, status
any changes in property file doesn't leads to reloading of logging configuration. On the contrary, it seems to be perfectly working in xml format
<Configuration status="TRACE" monitorInterval="5">
where whenever I do make any changes in .xml my log4j configuration is picked up and is verified via following log.
2016-06-17 14:43:17,267 Thread-5 DEBUG Reconfiguration started for context 1198108795 (org.apache.logging.log4j.core.LoggerContext#86be70a)
2016-06-17 14:43:17,268 Thread-5 DEBUG Not in a ServletContext environment, thus not loading WebLookup plugin.
2016-06-17 14:43:17,273 Thread-5 DEBUG Initializing configuration XmlConfiguration[location=/Users/userx/Desktop/logs/log4j2_prod.xml]
I also tried to upgrade Log4j version to 2.5 but still observe same behavior.

To add to Ralph's answer, this was fixed in Log4j 2.6. The corresponding ticket is https://issues.apache.org/jira/browse/LOG4J2-1263
Please use Log4j-2.6.1 or later.

This was a bug that has been fixed. I would suggest updating the latest log4j release.

Related

Issues in applicationContext.xml , SecurityConfig.xml and servlet-context.xml

I'm having three xml files and in all of them the schema versions are defined. However I removed all the version and kept it as default one, But I'm having these error messages and my beans are not getting intialized. Please refer the attached image to see the errors:
ApplicationContext.xml file
SecurityConfig.xml file
Servlet-context.xml file
Spring-version : 5.3.19
Java version - 17
Maven - 3.8.7
Wildfly - 25
I've also tried to make the schema version as 5.3.19, by making that error goes away but at the runtime same error comes. Please help me in resolving this.

Why explode log file excluding spring-boot-starter-logging?

I deployed a war project in a Tomcat and it works without any problem. So I tried to deploy same war project in another tomcat. To deploy in this new Tomcat I need to insert this exclusion in my pom.xml file:
spring-boot-starter-logging
this exclusion get a lot of log lines ... inserting exclusion I have a log line every 30 seconds. This is the log line :
2019-10-02 11:36:08 DEBUG HikariPool:404 - ProjectHikaryPool - Pool stats (total=10, active=0, idle=10, waiting=0)
Image
spring-boot-starter-logging is embedded in the spring boot starter web. Spring boot is not dedicated to a specific logging framework and the default one is logback as you can read in the docs. Enabeling the spring-boot-starter-logging or spring-boot-starter-web will print out all the system side debug information to the console. If you disable it the logs won't be printed. Why don't you expect this behaviour?
If you want to change the log level that is printed to the console you can use
logging.level.org.springframework.web=DEBUG
logging.level.org.hibernate=ERROR
for example as mentioned in the docs

spring boot logback-spring.xml maxFileSize not working with SizeAndTimeBasedRollingPolicy

I want to configure logging in spring boot application. I have configure logback-spring.xml. The sample of logback-spring.xml is located on here and sample of application-dev.properties file is located here When I just try to run spring boot application get below error:
java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.util.PropertySetter#5b7a5baa - Failed to invoke valueOf{} method in class [ch.qos.logback.core.util.FileSize] with value [{LOG_FILE_MAX_SIZE}]
ERROR in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy#2003496028 - maxFileSize property is mandatory.
If I replace <maxFileSize>{LOG_FILE_MAX_SIZE}</maxFileSize> with <maxFileSize>50MB</maxFileSize> application is running successfuuly
Try using the variable in your log filename. If it ("50MB") shows up in the filename, you know for sure that it is set.
I ran into this problem with the variables set in my pom.xml for profile "dev". I was using a separate profile "test" for my tests so the "dev" variables were not being set.
this will solve the issue. In logback.xml use $ with {attribute}
ex:- ${max.log.size}
make sure u have initialized max.log.size with values in application.properties.
It works!!

How to setup ebean log level with log4j

I'm using log4j and slf4j-log4j12 to print log in my project.
Problem is i don't want to show ebean's log.
I have read Ebean logging config documentation but it's for logback.
I have tried log4j.logger.io.ebeaninternal.server.transaction.JdbcTransaction=INFO. It's not work too.
Does anyone know how to config log4j for ebean to just printout [INFO] level or None
I solved my problem. This is my config for anyone who need it.
# Setup log level for Ebean
log4j.logger.io.ebean.SQL=INFO
log4j.logger.io.ebean.SUM=INFO
log4j.logger.io.ebean.TXN=INFO
log4j.logger.org.avaje.classpath.scanner=INFO

How to print configuration information of logback?

I have configuration the logback with specified custom logback.xml file, but the log it prints is not what I want.
This is my code to initial logback:
private void initLogBack() throws JoranException {
JoranConfigurator configurator = new JoranConfigurator();
configurator.setContext(createLogbackContext());
configurator.doConfigure(mycustomLogbackConf);
}
I think it may read some unexpected "logback.xml" files from somewhere I don't know. Is there any way to print all the configuration information that logback used?
e.g.
The configuration files it uses
The loggers defined
The debug levels defined
Is it possible?
logback 1.0.4 version has a fix with which you can set debug level at jvm level by using a property
-Dlogback.debug=true
Reference: http://jira.qos.ch/browse/LOGBACK-527
Hope it helps.

Categories

Resources