Develop Reference

Quarkus - Is there a way to empty the log file at every initiation instead of appending to it?

I want the log file to be empty every time I start the application. But I cannot find a way to do so. There is nothing stated as such in the Quarkus documentation (https://quarkus.io/guides/logging#quarkus-log-logging-log-config_quarkus.log.file-file-logging).
I would really appreciate if someone can tell me how to do it or suggest a workaround in case it is not possible.
This is the logging configurations in the application properties file
# Log
quarkus.log.category."com.helesto".level=DEBUG
quarkus.log.level=INFO
# Log File
quarkus.log.file.enable = true
quarkus.log.file.format = %d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c{3.}] (%t) %s%e%n
quarkus.log.file.path = logs/test.log

I configured quarkus to begin a new file on reboot.
As documented here you need to either set a max-file-size or configure a file-suffix for it to work.
This is my working configuration:
quarkus.log.file.enable= true
quarkus.log.file.path= /log/backend.log
quarkus.log.file.level= DEBUG
quarkus.log.file.format= %d{HH:mm:ss} %-5p [%c{2.}] (%t) %s%e%n
quarkus.log.file.rotation.file-suffix= .yyyy-MM-dd
quarkus.log.file.rotation.rotate-on-boot= true
quarkus.log.file.rotation.max-backup-index= 31
with this configuration it produces a daily log and begin a new file on reboot up to maximum 31 files.

logback same timestamp for different logs

I am using following log pattern property in log configuration of logback.
<property name="FILE_LOG_PATTERN" value="%d{yyyy-MM-dd HH:mm:ss.SSS} %5p ${PID:- } --- [%t] : [%X{requestContext}] [%X{transactionId}] - %m%n"/>
Unfortunately, when I log request and response, time stamp is exactly same. However when I manually checks, response takes more than 2 seconds
2016-09-12 09:57:39.925 DEBUG 5955 --- [http-nio-1980-exec-1] : Request:
2016-09-12 09:57:39.925 DEBUG 5955 --- [http-nio-1980-exec-1] : Response:
Since my code is not adding logging time, I believe I am missing something. What can it be?
logback is also taking up to 30 secs to log something. But i believe it is because of queue. And it has no relation with above issue.

I couldn't find solution for that. So I used two loggers to log the request and response. Unfortunately it dint work. So, finally, I broke the logging filter in 2 separate classes. I am not sure if it is logging the correct time. But at least the time is not same now.

How to apply log pattern to both SLF4J _and_ JUL?

I'm using logback and the JUL to SLF4J bridge (the latter for capturing third party libraries log statements that use Java Logging).
I get the log output from the third parties, but the logging pattern isn't what I specified for Logback. Should JUL and Logback use the same pattern that I specified in my logback.xml? Or do I need to set JUL separately? And finally, if I need to set JUL separately, is there a way to have a single place to define my log output pattern and have that go to JUL and Logback?
The setup I have looks like this:
In my main class I have a static block (at the top of the class) with these lines:
SLF4JBridgeHandler.removeHandlersForRootLogger();
SLF4JBridgeHandler.install();
My logback.xml looks like this:
<configuration>
<contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"/>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<Pattern>
%d{HH:mm:ss.SSS} [%-32thread] %-5level | %-80msg | %class.%method\(%file:%line\)%n
</Pattern>
</encoder>
</appender>
<root level="WARN">
<appender-ref ref="STDOUT"/>
</root>
</configuration>
Below are two lines of log output that I copied. You'll notice the first line is per the format I specified and the second line is not (because it is coming from JUL):
21:06:33.297 [ModelUpdateThread-1 ] INFO | view Molecules and Complexes took 1 ms for 17116 model elements | com.**[blanked out for privacy]**
Sat Nov 21 21:06:33 EST 2015 : com.tomsawyer.licensing.TSILicenseManager - setUseProxy
INFO: setUseProxy: false

Patterns set in Logback should be automatically applied to JUL... or rather, since the JUL log records are handed off to Logback for logging the pattern will apply.
The problem I was seeing turned out to be because the third party library (from tomsawyer) was by default writing its logs to both stdout and JUL. That is... Tomsawyer was using System.out to write log messages in addition to Logger.info. The clue that this was happening resides in the log level of my configuration (warn) and the output log level from Tomsawyer (info).
So indeed the Tomsawyer output was being sent to logback and then suppressed because the log level was configured at warn. And since Tomsawyer was also outputting to stdout with System.out... I still saw the message.

Log4j logging info messages without logging warn messages

I'm trying to log certain info messages onto a file but as soon as I run the application both warn and info messages are logged. Now, from what I've read from this site, you cannot log one without logging the other. Has anyone tried this before? If so, how did your properties file look like?
My properties file looks like this:
***** Set root logger level to INFO and its two appenders to stdout and R.
log4j.rootLogger=INFO, stdout, R
# ***** stdout is set to be a ConsoleAppender.
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
# ***** stdout uses PatternLayout.
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# ***** Pattern to output the caller's file name and line number.
log4j.appender.stdout.layout.ConversionPattern=%5p [%M has started] (%F:%L) - %m%n
/
# ***** R is set to be a RollingFileAppender.
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.R.File="folder where log will be saved"
log4j.appender.R.layout.ConversionPattern=%5p [%m has started] %c{2}.[%x] (%F:%L) %d{yyyy-MM-dd HH:mm:ss} - %m%n
# ***** R uses PatternLayout.
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%5p [%m has started] %c{2}.[%x] (%F:%L) %d{yyyy-MM-dd HH:mm:ss} - %m%n

AFAIK there's no standard way to suppress higher log levels than those you are interested in.
However, you might be able to use a custom appender to do that.
It might look similar to this:
public class MyAppender extends AppenderSkeleton {
protected void append(LoggingEvent event) {
if( event.getLevel() == Level.INFO ) {
//append here, maybe call a nested appender
}
}
}

The log level WARN is higher than INFO, and the logging configuration defines the minimum threshold level to be logged by the appender. So, all messages higher than that level will also be logged.
Hence, the WARN messages are expected. And I don't think you can configure it to the way you want.

If the WARN messages that should not be printed come from a different package than the INFO messages, then you can define different log levels for these packages. The first can specify level ERROR and the second INFO
it should look something like this:
log4j.logger.com.test.something=ERROR
log4j.logger.com.other.package=INFO
cheers

Why do you want to filter the WARN level? As peshkira said, you could use two different loggers for splitting/filtering your log output, or you could use tools like grep for filtering (offline) or you could simply remove the WARN logs from your code if your don't need them anyway.

As far as I understand, advanced filters like LevelMatchFilter and LevelRangeFilter can do the trick for you.
Thing worth keeping in mind though is that using these may require xml config instead of properties: Can't set LevelRangeFilter for log4j

how do I turn off logging in java c3p0 connection pooling lib?

hey all, I'm just getting started with c3p0 for database connection pooling. It's attaching itself to my log4j output currently. How do I set logging off or at least to SEVERE level only for c3p0? I tried tweaking the properties file but not sure it's being picked up properly.
any ideas on how best to turn it off?
thanks
UPDATE:
this seems to work in the log4j.properties file
log4j.logger.com.mchange.v2.c3p0.impl=INFO
log4j.logger.com.mchange=INFO

For those who are NOT using a configuration file, just to add the following in the code, before loading the connection pool.
Properties p = new Properties(System.getProperties());
p.put("com.mchange.v2.log.MLog", "com.mchange.v2.log.FallbackMLog");
p.put("com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL", "OFF"); // Off or any other level
System.setProperties(p);

If you use a log4j.xml file you can simple define a logger for the c3po package:
<logger name="com.mchange.v2.c3p0">
<level value="SEVERE"/>
</logger>
There are analogous methods for log4j.properties. I think it's just:
log4j.logger.com.mchange.v2.c3p0=SEVERE

I was getting messages like the following:
Tue Feb 12 13:42:01 EST 2013 INFO: Profiler Event: [FETCH] at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76) duration: 0 ms, connection-id: 67, statement-id: 23, resultset-id: 27
This made me think that C3P0 was logging these messages. Actually the message is coming from the mysql connector because I enabled profiling by using a connection string like this:
jdbc:mysql://localhost/database?profileSQL=true
Remove ?profileSQL=true to make it stop logging these messages.

I fixed problem with line of code:
com.mchange.v2.log.MLog.getLogger().setLevel(MLevel.INFO);
I am using log4j in my app.

You can set log level by adding following lines in log4j.xml
Logging at least at Error level is desired.
< category name="com.mchange" additivity="false">
< priority value="ERROR"/>
< appender-ref ref="ASYNC"/>
</ category>
If you really want to turn off c3P0 logging set property com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL=OFF
in c3p0-Config.properties
or you can directly set this in code as an System property System.setProperty("com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL",MLevel.OFF);

I am working on clojure, through korma and for the life of my I could not get any properties files to load (I am new to clojure so I blame myself). If you are in a similar boat, the following might help you out.
(System/setProperties
(doto (java.util.Properties. (System/getProperties))
(.put "com.mchange.v2.log.MLog" "com.mchange.v2.log.FallbackMLog")
(.put "com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL" "OFF")))
The is basically a clojure port of Philippe Carriere's answer above, thank you so much!