- logback-user - mailman3.qos.ch

Plugin execution not covered by lifecycle
by Leonardo Souza 17 Jul '13

17 Jul '13

How to deal with this? Do i have to configure m2e plugin? Description Resource Path Location Type Plugin execution not covered by lifecycle configuration: org.apache.felix:maven-bundle-plugin:2.1.0:manifest (execution: bundle-manifest, phase: process-classes) pom.xml /logback-access line 127 Maven Project Build Lifecycle Mapping Problem commit 72d76165ac3272d8e6d466e258de6449e89d30f3 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Jul 3 13:24:11 2013 +0200 document LOGBACK-617 fix, minor changes -- Leonardo S Souza Amtera Semantic Technologies Rua da Quitanda, 194, sala 1201 - Centro Rio de Janeiro - RJ - Brasil Tel: + 55 21 2213 3220 Cel: + 55 21 9877 7081 www.amtera.com.br

2 1

Re: [logback-user] class name is displayed incorrectly for java inner classes
by Stuart Rossiter 17 Jul '13

17 Jul '13

On 17 July 2013 09:23, David Roussel <nabble(a)diroussel.xsmail.com> wrote: > Andy, > > The name of the logger is set when the logger is created form the > LoggerFactory. You are creating LOG in your outer class. Try creating > another logger in your inner class. > Yes, it is slightly subtle that the loggers just have the name you pass to them: they don't 'know' the class structure of what's calling them, and we don't want them to since we might want our own arbitrary set of loggers where each covers some specific set of classes (say). Even though you are using the getLogger(Class clazz) form, it still just generates a logger name, which multiple classes could reuse if they wanted to (by passing that name in their Logger setup code). BTW (general question to the mailing list): this code suggests that the getLogger(Class clazz) form sets the logger name using the source file name (e.g., SLF4JConsoleTest.java here, cf. SLF4JConsoleTest). I've always used the getLogger(String name) form, passing SLF4JConsoleTest.class.getCanonicalName(), or getSimpleName() if I don't want the full name. (It might even be that I changed to that because of this ugly .java suffix, though I can't explicitly remember that.) Is there a reason for that? If it's to link to the file producing it (rather than the class), that doesn't seem very useful without a path. Apologies if this is stated somewhere obvious in the manual. Stuart -- ________________________________ Stuart Rossiter stuart.p.rossiter(a)gmail.com Research Fellow: EPSRC Care Life Cycle Project http://www.southampton.ac.uk/clc

2 4

Logback defaulting to debug mode for some third party libraries
by amit shah 16 Jul '13

16 Jul '13

We use slf4j and logback for logging in our java ee web application. Recently in order to move these libraries to a common location in the glassfish app server (to glassfish\lib directory specifically) we made a couple of configuration changes. We made changes in the web.xml file to add JNDI entries and renamed the logback.xml to logback-<context-name>.xml as specified in here <http://logback.qos.ch/manual/loggingSeparation.html>. The logback-<context-name>.xml is placed in WEB-INF\classes directory. After this change, logging for hibernate and http-client libraries is defaulting to debug mode and hence there is lot of logging being done. The root logger has INFO log level and there are no specific loggers defined for hibernate & http-client libraries. If I revert this change i.e. remove the jndi entry in web.xml and rename the configuration file to logback.xml, only INFO logs are logged as expected. Any suggestions on what could be the issue? Thanks, Amit.

2 2

Use multiple receivers to log multiple remote server appenders
by Chris Hamilton 15 Jul '13

15 Jul '13

I have multiple web servers configured in a cluster. I have set up a "server" appender on each instance of the application. I have used the Receiver example to create a program that will connect to the remote server appenders and log the messages received from each cluster member to a single remote file. The problem I have is identifying the source server in the remote remote log file. What I'm looking for is a way to identify the source server of each message. I have enhanced the SocketReceiver and added a field called ReceiverAlias which is set in logback.xml. Currently I am prepending this string to the log message. This works but doesn't look or feel right. I'm thinking that there ought to be a better way. Is there an established pattern for this use case? Thanks

1 0

Too much time for processing logback.xml
by Arioco 13 Jul '13

13 Jul '13

Hello. I have just discovered SLF4J and Logback and I am testing it in local before using it in my projects. I downloaded SLF4J 1.7.5 and Logback 1.0.13, created a new project in Eclipse with workspace in local, put slf4j-api-1.7.5.jar, logback-classic-1.0.13.jar and logback-core-1.0.13.jar in CLASSPATH and wrote a very simple test class: package com.compa.prueba.logging.slf4j; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class Pruebas { private final static Logger logger = LoggerFactory.getLogger(Pruebas.class); public static void main(String... args) { logger.info("let me see..."); logger.debug("\\{} {} {} {} {} {}", "1", 2, new Double(3), "4", "5"); } } Everything was just fine, execution time was almost nothing (of course) until I added a logback.xml file. Since then I got a 10 secs longer startup time. I found a post with a problem very similar to mine, but with no answer to me: http://logback.10977.n7.nabble.com/Elongated-system-startup-time-because-of… I have been doing a bunch of tests and I think problem is XML-processing-time, and I don't have a clue about why. Briefing: * Replace Logback with NOP: execution time 0.x milisecs * Delete logback.xml file from classpath: execution time 0.x milisecs * Adding debug="true" to configuration tag. Here is where I am now. My actual logback.xml file is: <?xml version="1.0" encoding="UTF-8"?> <configuration debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <root level="debug"> <appender-ref ref="STDOUT" /> </root> </configuration> And after execution my console shows this: 12:55:41,819 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 12:55:41,819 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] *12:55:41,819* |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/Volumes/Macintosh%20HD/workspace/PruebaLogging/bin/logback.xml] *12:55:51,925* |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 12:55:51,929 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 12:55:51,951 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 12:55:51,998 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 12:55:51,999 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 12:55:51,999 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 12:55:52,001 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4b9237a - Registering current configuration as safe fallback point 2013-07-13 12:55:52.005 INFO c.compa.prueba.logging.slf4j.Pruebas - let me see... 2013-07-13 12:55:52.008 DEBUG c.compa.prueba.logging.slf4j.Pruebas - {} 1 2 3.0 4 5 I highlighted two timestamps in log output just for pointing the 10 secs difference. A very curious fact is that delay is always 10 secs, no matter how many times I execute. I hope I have write information enough for you to help me. Thank you very much to all. Regards Carlos -- View this message in context: http://logback.10977.n7.nabble.com/Too-much-time-for-processing-logback-xml… Sent from the Users mailing list archive at Nabble.com.

1 0

Double logging in console
by sadiq81 12 Jul '13

12 Jul '13

Hey I have been trying like crazy to figure out what is going. All my console logs are coming out twice. Perhaps someone can tell me what idiot mistake i have made. <?xml version="1.0" encoding="UTF-8"?> <configuration debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <Pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern> </encoder> </appender> <logger name="dk.eazyit.eazyregnskab" level="DEBUG"> <appender-ref ref="STDOUT"></appender-ref> </logger> <root level="WARN"> <appender-ref ref="STDOUT"/> </root> </configuration> -- View this message in context: http://logback.10977.n7.nabble.com/Double-logging-in-console-tp12662.html Sent from the Users mailing list archive at Nabble.com.

2 2

Configuring Exception logging
by Daniel Serodio (lists) 12 Jul '13

12 Jul '13

Suppose I have this Java code: try { // ... } catch (Exception ex) { logger.error("Something went wrong", ex); } I want to choose at runtime if a specific Logger should log the exception's stacktrace or just its message. Is this possible with Logback? Thanks in advance, Daniel Serodio

1 0

Basic example of programmatically setting the configuration
by Roger Thomas 12 Jul '13

12 Jul '13

I've just started to set up an environment with logback, but found examples for programmatically configuring logback limited, or a mix of solutions for a number of different logger interfaces. As such I hope that the code below helps someone in the future as an example. It may not be the best code on the planet but what it demos is - Select the root logger so that the configuration becomes the default. - Sets up a RollingFileAppender - Sets up a FixedWindowRollingPolicy - Sets up a SizeBasedTriggeringPolicy - Sets up a PatternLayoutEncoder To be honest I'm not at the point of fully understanding all the steps so can't provide full docs for the example (yet). package org.utils; import ch.qos.logback.classic.encoder.PatternLayoutEncoder; import ch.qos.logback.classic.spi.ILoggingEvent; import ch.qos.logback.core.rolling.FixedWindowRollingPolicy; import ch.qos.logback.core.rolling.RollingFileAppender; import ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy; import ch.qos.logback.core.util.StatusPrinter; import ch.qos.logback.classic.Logger; import ch.qos.logback.classic.LoggerContext; import org.slf4j.LoggerFactory; public class setupLogging { public static void logbackInit() { Logger rootLogger = (Logger)LoggerFactory.getLogger(Logger.ROOT_LOGGER_NAME); LoggerContext loggerContext = rootLogger.getLoggerContext(); loggerContext.reset(); RollingFileAppender<ILoggingEvent> rfAppender = new RollingFileAppender<ILoggingEvent>(); rfAppender.setContext(loggerContext); rfAppender.setFile("log output.log"); FixedWindowRollingPolicy fwRollingPolicy = new FixedWindowRollingPolicy(); fwRollingPolicy.setContext(loggerContext); fwRollingPolicy.setFileNamePattern("log output-%i.log.zip"); fwRollingPolicy.setParent(rfAppender); fwRollingPolicy.start(); SizeBasedTriggeringPolicy<ILoggingEvent> triggeringPolicy = new SizeBasedTriggeringPolicy<ILoggingEvent>(); triggeringPolicy.setMaxFileSize("5MB"); triggeringPolicy.start(); PatternLayoutEncoder encoder = new PatternLayoutEncoder(); encoder.setContext(loggerContext); encoder.setPattern("%-4relative [%thread] %-5level %logger{35} - %msg%n"); encoder.start(); rfAppender.setEncoder(encoder); rfAppender.setRollingPolicy(fwRollingPolicy); rfAppender.setTriggeringPolicy(triggeringPolicy); rfAppender.start(); rootLogger.addAppender(rfAppender); // generate some output StatusPrinter.print(loggerContext); rootLogger.debug("hello tt"); } }

2 1

Splitting log files by session
by Andreas Johnsen 12 Jul '13

12 Jul '13

I am developing an application where I need to make separate log files for each time a certain process is run. This process can have multiple instances at once. Preferably I would like a separate method for these types of logs (like info, warning, trace etc) but I would be okay with simply using trace for these logs. I would still like any error or warning that spawns in this process to be logged to the standard error file (global for entire project). I'm trying to configure logback to do this for me. My initial idea was to create my own appender, and somehow figure out which process the log request was coming from, but I ran into a problem actually doing that, since I apparently cannot pass anything useful to the appender in runtime? Or rather I'm not sure how to keep track of and always use the appender that belongs to that particular process. I then proceeded to get lost in the vast number of classes and I am now looking at perhaps modifying a RollingPolicy to do my bidding. Any ideas or clarifications on this topic would be very welcome.

3 3

GSiftingAppender
by Jürgen Hofmann 10 Jul '13

10 Jul '13

Hi, I make heavy use of the GSiftingAppender but found that is no longer supported since 1.0.12. Currently I stick with 1.0.11 for this reason, but don't feel very comfortable with it on long term. I actually prefer the groovy configuration and I believe the things I'm doing can not easily be achieved with xml configuration. What options do I have? Any hints on how to migrate to the current version? Many thanks Jürgen

1 0