- logback-user - mailman3.qos.ch

How to control WebApp logging by Tomcat control files
by Ulrich 21 Apr '14

21 Apr '14

Being new to WebApps, I started with TOMCAT 7 and try to do Logging with LOGBACK. I'm doing this already on WebApp Basis by adding all necessary resources to the WebApp Environment (WEB-INF). Here I'm using the ConsoleAppender and all messages are captured then by the default java.util.logging and stored to a file (just TOMCAT 7 default configuration). I found the explanation to replace java.util.logging by logback (http://logback.qos.ch/access.html) and got it running. But don't understand how it works. 1. I tried the sample configuration "Example 2: RollingFileAppender" but am still wondering where it's stored. Though the StatusMessageServlet displays some messages, I can't figure out from where they are retrieved. Only specifying <file>${catalina.base}/logs/access.log</file> directed the file to a known location. 2. The access.log was not zipped as indicated by the definition "<fileNamePattern>/access.%d{yyyy-MM-dd}.log.zip</fileNamePattern>" nor did it contain the messages displayed by the StatusMessageServlet 3. I've no clue how to control the WebApp logging by the central configuration file. I would prefer controlling logging be central config files rather than be files maintained by the WebApp itself. How can I manage to connect my WebApp to the central logback.xml I hope the questions make any sense. I'm lacking some fundamental understanding with logging by Tomcat. -- View this message in context: http://logback.10977.n7.nabble.com/How-to-control-WebApp-logging-by-Tomcat-… Sent from the Users mailing list archive at Nabble.com.

2 2

Disable scanning of logback.xml during initialization
by Simon Wong 17 Apr '14

17 Apr '14

Hi, I am using logback with Spring logback extension. The exact log location is determined at runtime through the "webAppRootKey" context param, that mentioned in WebLogbackConfigurer In web.xml, <context-param> <param-name>webAppRootKey</param-name> <param-value>myApp.root</param-value> </context-param> In logback.xml, <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${myApp.root}/../../logs/${FILE_NAME_PREFIX}.%d.log.zip</FileNamePattern> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{32} - %msg%n</pattern> </encoder> </appender> The issue is during logback initialization, it will scan the logback.xml automatically but the ${myApp.root} is not yet resolved, due to Spring Web Application Context is initialized lazily. The log entry could not write to log file successfully. The workaround solution is the program "touch" the logback.xml again during @PostConstruct phase after Spring Web Application Context is constructed. Logback will scan the change of logback.xml some time later and at that time the ${myApp.root} is correctly resolved. e.g. @PostConstruct void init() { try { ClassPathResource logbackResource = new ClassPathResource(logback.xml); File logbackConfigFile = logbackResource.getFile(); FileUtils.touch(logbackConfigFile); } catch (IOException ioe) { throw new RuntimeException(ioe); } } Is there a way that I could disable the auto scanning of logback.xml during initialization? Or defer until ch.qos.logback.ext.spring.web.LogbackConfigListener is well configured?

1 0

using JDK 1.6 in logback
by Ceki Gulcu 16 Apr '14

16 Apr '14

Hi All, Given that logback already requires JDK 1.6 to compile, and the recent release of Java 8, and that JDK 1.5 is no longer supported by Sun/Oracle, I think it's about time we move to JDK 1.6 for logback. Any objections or comments? Many thanks for your input. -- Ceki

5 5

Delete log file in runtime and slf4j+logback doesnt create it again
by Raghu Prabhudeva 11 Apr '14

11 Apr '14

Hi, Im facing this problem while using version 1.0.13 of logback. "Delete log file in runtime and slf4j+logback doesnt create it again" Can you please suggest some way of resolving this issue. Thanks Raghu

2 1

Logback without SLF4j
by ? 11 Apr '14

11 Apr '14

Hello Logback community, I'd like to know if it is possible to use logback without any dependency to SLF4j. I appreciate SLF4J very much, but my project setup is difficult with many third party libraries. Thanx.

2 1

How to close log files?
by Arne Schirmacher 11 Apr '14

11 Apr '14

I am using the sifting appender to write a new log file for each pass of my program. The problem is that each log file appears to be still open even after the next log file is created. It is not possible to delete the log file. Windows reports that "the file is still open in Java(TM) platform SE binary". Only after shutting down the program I can delete the log files. Please advise how to close the log file after I am done with it so that I can delete it later.

1 0

Re: [logback-user] Logback-user Digest, Vol 31, Issue 5
by Thom DeCarlo 11 Apr '14

11 Apr '14

I agree with David. Go straight to 1.7. > On Apr 8, 2014, at 7:31 AM, David Tkaczyk <djt69b(a)gmail.com> wrote: > > Skip 1.6 and go to 1.7. > >> On Apr 8, 2014 6:00 AM, <logback-user-request(a)qos.ch> wrote: >> Send Logback-user mailing list submissions to >> logback-user(a)qos.ch >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://mailman.qos.ch/mailman/listinfo/logback-user >> or, via email, send a message with subject or body 'help' to >> logback-user-request(a)qos.ch >> >> You can reach the person managing the list at >> logback-user-owner(a)qos.ch >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Logback-user digest..." >> >> Today's Topics: >> >> 1. using JDK 1.6 in logback (Ceki Gulcu) >> >> >> ---------- Forwarded message ---------- >> From: Ceki Gulcu <ceki(a)qos.ch> >> To: logback users list <logback-user(a)qos.ch> >> Cc: >> Date: Tue, 08 Apr 2014 08:33:32 +0200 >> Subject: [logback-user] using JDK 1.6 in logback >> Hi All, >> >> Given that logback already requires JDK 1.6 to compile, and the recent >> release of Java 8, and that JDK 1.5 is no longer supported by >> Sun/Oracle, I think it's about time we move to JDK 1.6 for >> logback. Any objections or comments? >> >> Many thanks for your input. >> -- >> Ceki >> >> >> _______________________________________________ >> Logback-user mailing list >> Logback-user(a)qos.ch >> http://mailman.qos.ch/mailman/listinfo/logback-user > _______________________________________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user

2 1

Re: [logback-user] Logback-user Digest, Vol 31, Issue 5
by David Tkaczyk 08 Apr '14

08 Apr '14

Skip 1.6 and go to 1.7. On Apr 8, 2014 6:00 AM, <logback-user-request(a)qos.ch> wrote: > Send Logback-user mailing list submissions to > logback-user(a)qos.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qos.ch/mailman/listinfo/logback-user > or, via email, send a message with subject or body 'help' to > logback-user-request(a)qos.ch > > You can reach the person managing the list at > logback-user-owner(a)qos.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Logback-user digest..." > > Today's Topics: > > 1. using JDK 1.6 in logback (Ceki Gulcu) > > > ---------- Forwarded message ---------- > From: Ceki Gulcu <ceki(a)qos.ch> > To: logback users list <logback-user(a)qos.ch> > Cc: > Date: Tue, 08 Apr 2014 08:33:32 +0200 > Subject: [logback-user] using JDK 1.6 in logback > Hi All, > > Given that logback already requires JDK 1.6 to compile, and the recent > release of Java 8, and that JDK 1.5 is no longer supported by > Sun/Oracle, I think it's about time we move to JDK 1.6 for > logback. Any objections or comments? > > Many thanks for your input. > -- > Ceki > > > _______________________________________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user >

1 0

Rolling Appender Question
by Jeremy Kane 04 Apr '14

04 Apr '14

I have the following configuration in code (see below), and it is logging as expected, but it never rolls over to a new file, the one file just keeps growing. Can someone please help me out with what's wrong with my config? Alternately (or maybe even "preferably"), I'd like to roll over after the file reaches a certain size, and not worry about the date rollover at all, but I haven't had any luck with that either. If someone could help me out with that too (or instead), I'd greatly appreciate it! Thanks! Jeremy Kane My config code: LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); loggerContext.reset(); // Rolling Log Appender String fileDirectory = Constants.getFileDirectory(context); RollingFileAppender<ILoggingEvent> rollingFileAppender = new RollingFileAppender<ILoggingEvent>(); rollingFileAppender.setContext(loggerContext); rollingFileAppender.setAppend(true); rollingFileAppender.setFile(fileDirectory + "/log.txt"); TimeBasedRollingPolicy<ILoggingEvent> rollingPolicy = new TimeBasedRollingPolicy<ILoggingEvent>(); rollingPolicy.setMaxHistory(2); rollingPolicy.setFileNamePattern(fileDirectory + "/log.%d.txt"); rollingPolicy.setParent(rollingFileAppender); rollingPolicy.setContext(loggerContext); rollingPolicy.start(); rollingFileAppender.setRollingPolicy(rollingPolicy); PatternLayoutEncoder fileEncoder = new PatternLayoutEncoder(); fileEncoder.setContext(loggerContext); fileEncoder.setPattern("%d{h:mm:ss} %level - %msg%n"); fileEncoder.start(); rollingFileAppender.setEncoder(fileEncoder); rollingFileAppender.start(); // LogCat Appender PatternLayoutEncoder logcatEncoder = new PatternLayoutEncoder(); logcatEncoder.setContext(loggerContext); logcatEncoder.setPattern("%msg%n"); logcatEncoder.start(); PatternLayoutEncoder tagEncode = new PatternLayoutEncoder(); tagEncode.setContext(loggerContext); tagEncode.setPattern(tag); tagEncode.start(); LogcatAppender logcatAppender = new LogcatAppender(); logcatAppender.setContext(loggerContext); logcatAppender.setEncoder(logcatEncoder); logcatAppender.setTagEncoder(tagEncode); logcatAppender.start(); // add the newly created appenders to the root logger; // qualify Logger to disambiguate from org.slf4j.Logger ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) LoggerFactory.getLogger(Logger.ROOT_LOGGER_NAME); root.setLevel(level); root.addAppender(rollingFileAppender); root.addAppender(logcatAppender); // print any status messages (warnings, etc) encountered in logback config StatusPrinter.print(loggerContext);

1 0

Release of logback version 1.1.2
by Ceki Gülcü 04 Apr '14

04 Apr '14

Hello all, The logback team is happy to announce the release of logback version 1.1.2. It contains many bug fixes and improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details about this release. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

3 5