- logback-user - mailman3.qos.ch

Programmatic logback Configuration
by Chad La Joie 07 Nov '07

07 Nov '07

I have an application that ships with two logging configuration files; a default logback.xml file (DLF) included in the application JAR and a user-editable file (UEF) installed on the filesystem with other application configuration files. The DLF is used when the application is starting but before the code to read in the UEF is executed. My current code for reading in the UEF looks like this: LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); loggerContext.shutdownAndReset(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(loggerContext); configurator.doConfigure(configuration.getInputStream()); loggerContext.start(); The behavior I'm seeing though is note quite what I expected. Assume the DLF contains a console appender and a logger definition for package "foo". The behavior I see when the UEF is loaded is: - Changes to the logger FOO (e.g. changes in the logging level, addition/removal of appenders, etc.) are picked up and become active. - Declaration of new appenders are picked up and become active (e.g. if a new file appender is defined I can see it creating the new log file). - Declaration of new loggers are *not* picked up. If, for example, a logger "bar" is defined and given the same console appender as "foo" no output from "bar" is sent to the console. Is this expected behavior? Is my code wrong (I've tried the same code without the start() or shutdownAndReset() method calls)? Any help would be appreciated. -- SWITCH Serving Swiss Universities -------------------------- Chad La Joie, Software Engineer, Security Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 75, fax +41 44 268 15 68 chad.lajoie(a)switch.ch, http://www.switch.ch

2 3

logback.xml with Tomcat 5.5
by jendicott 29 Oct '07

29 Oct '07

I am having trouble getting slf4j/logback to work in my webapp that is getting deployed in Tomcat. I have changed all of my application classes to import and use the slf4j classes, I compile with them and then deploy a war that Tomcat expands into the webapp dir. My logback.xml file shows up in the WEB-INF/classes directory of my application but no log file gets created/written to. I used the log4j Properties translator page to get this xml: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="F" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/srvc2.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{dd MMM yyyy HH:mm:ss} %c{3}:%L - %m%n</pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>'.'yyyy-MM-dd</fileNamePattern> </rollingPolicy> </appender> <logger name="com.opensymphony.oscache"> <level value="ERROR"/> </logger> ... in here there a bunch more logger elements that set the level for various things. <logger name="com.vizible"> <level value="DEBUG"/> </logger> <root> <level value="INFO"/> <appender-ref ref="F"/> </root> </configuration> I am expecting to see a file in the Tomcat logs directory called "srvc2.log" but I don't see anything and none of the regular Tomcat logs show anything. I am running Tomcat as a service in windows XP. Am I missing something?? Any suggestions would be appreciated. -- View this message in context: http://www.nabble.com/logback.xml-with-Tomcat-5.5-tf4713692.html#a13474065 Sent from the Slf4J - user mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/logback.xml-with-Tomcat-5.5-tf4714034.html#a13475065 Sent from the Logback User mailing list archive at Nabble.com.

1 0

Creating empty directory for log automatically
by Daniel Rossi 25 Oct '07

25 Oct '07

Hi there, im trying to setup loggers programatically and noticed that logback / log4j wont create the empty directory for you using rollingfileappender. Here is what ive had to do to get the parent directory recursively created because i wont be sure what the parent directory of the logger will be until its created. Is there a better way ? LoggerContext lc = (LoggerContext) logStats.getLoggerContext(); W3CAccessLayout layout = new W3CAccessLayout(); layout.setContext(lc); layout.start(); RollingFileAppender<LoggingEvent> appender = new RollingFileAppender<LoggingEvent>(); appender.setContext(lc); appender.setImmediateFlush(true); appender.setName(appenderName); appender.setLayout(layout); TimeBasedRollingPolicy policy = new TimeBasedRollingPolicy(); policy.setContext(lc); policy.setFileNamePattern(path + logFilePattern); policy.setParent(appender); policy.setCurrentTime(System.currentTimeMillis()); policy.start(); File file = new File(policy.getNewActiveFileName()); File dir = new File(file.getParent()); dir.mkdirs(); appender.setRollingPolicy(policy); appender.start(); logStats.addAppender(appender);

1 0

custom logger / appender / layout
by Daniel Rossi 23 Oct '07

23 Oct '07

Hi there I have a custom spring app I need to setup an access log for. I'm needing it in W3C format for reporting purposes. I'm porting it to logback from log4j because the server the application is in is now using it. How is it possible to create a custom logger with custom log level methods, a custom level class with levels higher than FATAL so it doesnt get mixed up with the root logger. Im also needing to create it all programatically so setup the logger when requested because i need to produce a logger for each context path in the spring app so i get a different log file for each context. Issue ive experienced so far porting my code is that the layout, rollingpolicy and appender all need contexts set to it or else it complains about no context set ? I'm also needing to work out how it would be possible to create a custom even / layout / pattern convertor to obtain particular statistical details from the server similar to the implementations for tomcat and jetty though its a video server and not sure if its running in a servlet as such. Ive worked out so far there is possibilities to add fields set in the MDC to the file header aswell as in the pattern string for the file appender. As of now no log file is being set. Here is the code so far. MDC.put("x-event", "stop"); MDC.put("x-category", "stream"); logStats = (Logger)LoggerFactory.getLogger(loggerName); if (null == logStats.getAppender(appenderName)) { layout = new PatternLayout(); layout.setPattern("%X{x-event} %X{x-category} - %msg%n"); layout.setFileHeader("x-event \t x-category"); layout.setContext(logStats.getLoggerContext()); layout.start(); appender = new RollingFileAppender(); policy = new TimeBasedRollingPolicy(); policy.setContext(logStats.getLoggerContext()); policy.start(); appender.setContext(logStats.getLoggerContext()); appender.setName(appenderName); appender.setLayout(layout); policy.setFileNamePattern(path + logFilePattern); appender.setRollingPolicy(policy); appender.start(); logStats.addAppender(appender); } Currently I have to call logStats.error("stop"); In my log4j class it was logStats.stop("message"); which present the stop level inside it, but cant find and implementation to subclass as yet. Let me know thanks.

1 0

RE: "Watching" the config file
by Ted Graham 19 Oct '07

19 Oct '07

Can anyone tell me if "watching" the config file for changes is planned for logback? Being unable to control the logging configuration without a restart is a big problem for my applications. Thanks, Ted From: Ted Graham [mailto:tgraham@ConcordEnergy.com] Sent: Thursday, October 04, 2007 2:22 PM To: 'logback-user(a)qos.ch' Subject: "Watching" the config file One of my favorite log4j features is the ability to watch the config file and reload it when it has changed. Any plans to support that in logback? I searched this list's archives and found some discussion of this feature, but nothing definitive. Thanks, Ted

3 4

lower-upper level limits
by Karnok Dávid 13 Oct '07

13 Oct '07

Hi, Is there a way to setup the loggers that any log message between DEBUG and WARN goes to System.out and ERROR+FATAL goes to System.err only? -------------------------------- Karnok Dávid PhD Student Engineering Management and Intelligence laboratory, Computer and Automation Research Institute, Hungarian Academy of Sciences http://www.sztaki.hu http://www.emi.sztaki.hu

2 1

Multiple log files
by c. 12 Oct '07

12 Oct '07

Hi, I have a couple of applications running on one tomcat instance. I use the following xml file for each application substituting contextX for the application name, however, when I start tomcat only one context is initialized and all log messages are sent to that context. Is it possible to have a log file for each application in a tomcat instance? Thanks, Chris. [code] <?xml version="1.0" encoding="UTF-8" ?> <configuration> <appender name="stdout" class="ch.qos.logback.core.ConsoleAppender"> <rollingPolicy class=" ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <FileNamePattern>/var/log/tomcat6/catalina.%i.out</FileNamePattern> <MinIndex>1</MinIndex> <MaxIndex>7</MaxIndex> </rollingPolicy> <triggeringPolicy class=" ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>5MB</MaxFileSize> </triggeringPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d %-5level [%thread] %class | %msg%n</pattern> </layout> </appender> <appender name="contextX" class=" ch.qos.logback.core.rolling.RollingFileAppender"> <File>/var/log/tomcat6/contextX.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>/var/log/tomcat6/contextX.%d.log</FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{ISO8601} %-5level [%thread] %class | %msg%n</pattern> </layout> <Encoding>UTF-8</Encoding> <BufferedIO>false</BufferedIO> <ImmediateFlush>true</ImmediateFlush> </appender> <logger name="org.springframework" additivity="false"> <level value="WARN"/> <appender-ref ref="contextX" /> </logger> <logger name="com.contextX" additivity="false"> <level value="WARN"/> <appender-ref ref="contextX" /> </logger> <logger name="org.hibernate" additivity="false"> <level value="WARN"/> <appender-ref ref="contextX" /> </logger> <logger name="org.apache.velocity" additivity="false"> <level value="WARN"/> <appender-ref ref="contextX" /> </logger> <logger name="org.acegisecurity" additivity="false"> <level value="INFO"/> <appender-ref ref="contextX" /> </logger> <logger name="org.directwebremoting" additivity="false"> <level value="WARN"/> <appender-ref ref="contextX" /> </logger> <logger name="org.apache" additivity="false"> <level value="WARN"/> <appender-ref ref="stdout" /> </logger> <root> <level value="WARN"/> <appender-ref ref="stdout"/> </root> </configuration> [code]

1 0

Comparison between log4j and logBack
by ivancaspeta＠cox.net 04 Oct '07

04 Oct '07

Hi, We, myself included, just recently performed some research of the various logging tools available for Java; for whatever reason we did not include LogBack (honestly I did not read about it until today!). Anyways, as you can imagine, we have chosen log4j as our tool for logging, but we have not started implementation as of yet (we would be replacing an in-house tool and there are some other things to iron out first), so I would like to ask if there is a comparison matrix/table/doc between log4j and logBack. Some of our selection criteria include: 1. Several trace levels such as Fatal, Error, Warning, Info, Debug, Verbose, etc. 2. Ability to apply multiple filters, for example, have VERBOSE tracing turned on for Business Logic, and Terse for DAOs, and Error for everything else. 3. Alternate modes for output 4. Automatic method/class resolution, so I don’t have to enter that in the code 5. Ability to collect trace remotely 6. helper methods for string substitution 7. Ability to route trace to different files … put all Errors in File A, and at the same time Events and Errors in File B. 8. Log other attributes like Thread Id, Class, etc. 9. Low overhead to performance, “No logging” and “Logging, but disabled” should perform about the same, within 5% of each other. 10. Ability to turn logging on/off without re-starting 11. Ability to change logging levels while app is running; i.e., don't need to restart 12. Can be bundled at no cost, licensing is acceptable. 13. Configuration should not be rocket science 14. Chainsaw integration/support 15. UDP Support 16. Ability to trace a context, like an Item (NDC). I am reading as much doc as I can, but I would like to know why should we use logBack instead of log4j as the latter is widely used and popular among the Java community. Thanks for any input provided. Ivan C

1 0

"Watching" the config file
by Ted Graham 04 Oct '07

04 Oct '07

One of my favorite log4j features is the ability to watch the config file and reload it when it has changed. Any plans to support that in logback? I searched this list's archives and found some discussion of this feature, but nothing definitive. Thanks, Ted

1 0

logback initialization "à la" Spring
by Davide Baroncelli 28 Sep '07

28 Sep '07

Hi, I'm thinking about moving to logback after a life happily spent using log4j: nevertheless I'm having problems understanding if there's a way to initialize it in a similar way as we did with log4j. What I do not want to do is put a configuration file under the WEB-INF/classes dir in my webapp: all of our configuration files are stored under WEB-INF/cfg, and we want to continue this way. I see that logback has a way to define contexts through jndi, but we do not want to ask our system administrators to change the config of our weblogic clusters just because we think about introducing a new library: is there another way? What I'd like to obtain is something like we did with Spring's Log4jConfigListener: simply define into the web.xml a listener which configures the logging subsystem at startup time using the xml file indicated by a servlet context parameter. Is there something like that? I was thinking about writing a class by myself, but I see no way to do it without triggering the BasicConfigurator part in the static initialize method of StaticLoggerBinder. Thank you, Davide Baroncelli P.s.: let me express my disagreement for logback and sl4j not supporting neither the FATAL logging level nor automatic reloading of config files. -- View this message in context: http://www.nabble.com/logback-initialization-%22%C3%A0-la%22-Spring-tf45279… Sent from the Logback User mailing list archive at Nabble.com.

3 4