February 2007 - logback-user

An OSGi bundle for logback?
by John E. Conlon 14 Sep '07

14 Sep '07

Are there any plans for a logback OSGi bundle in the foreseeable future? ;-)

3 3

Using logback in tomcat
by Michael Abato 17 Apr '07

17 Apr '07

I'm successfully using logback with Tomcat and have a small suggestion that will help people with complex deployments: look for logback-access.xml in system property catalina.base rather than catalina.home. Tomcat is intentionally setup such that multiple instances (java VMs) can be running off the same copy of the tomcat distribution and set up private CATALINA_BASE directories for server config, logs, temp space, etc. Such setups will naturally want to configure logback in CATALINA_BASE, not in the (potentially read-only) CATALINA_HOME. In cases where the user does *not* set CATALINA_BASE, it takes the same value as CATALINA_HOME (which is generally the same as TOMCAT_HOME). I've patched the source of LogbackValve.java to do this and it works well. The change of "catalina.home" to "catalina.base" is to trivial for a formal patch... On a related note, I've also configured tomcat to use log4j/logback for internal logging, which also works quite well. I noticed in a previous post you "don't recommend this at this time" and would like to know the reason(s). Routing *all* logging through one logger/one config, which in turn can separate "live" logs from rotated out "archive" logs in a separate directory is a godsend. I'm assuming it is because doing this requires mucking around with the tomcat startup scripts to replace ACL from the very beginning of the tomcat boot process. I'd already created a "boot" directory with a dynamic set of jar's and classes (for unrelated reasons) so switching ACL to log4j/logback was pretty trivial for me. Is there more to the reluctance than the fact that there is no "drop in" way to do it? If there's interest, I can tidy up my tomcat patch and post the details. -- View this message in context: http://www.nabble.com/Using-logback-in-tomcat-tf2890321.html#a8074672 Sent from the Logback User mailing list archive at Nabble.com.

2 2

Logback configuration
by Hausherr, Jens 15 Mar '07

15 Mar '07

Hi, lgoback seems to solve some problems that log4j has, but I did not yet find the answer to my most pressign question: Does logback handle multiple configurations in a controllable manner? The crucial problem with log4j was its great propularity not only with application developers but also with library developers that sometimes packed an log4j confguration file into their jars. So in almost every project it could happen that one did configure log4j and only get strange or even no output because ther is some other log4j configration overriding the one intended by oneself. If logback improves this behavior of log4j I'd be switching immediately with flying colors! Regards, jens This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

5 8

Re: logback: worthy successor to log4j
by Ceki Gülcü 22 Feb '07

22 Feb '07

Hi Tomek, Logback is developed using Maven 2. Moreover, logbacks deployment repository is syncronized with ibiblio. Thus, about 4 hours after a release becomes public, it percolates on ibiblio. The latest version is 0.9 which is available on ibiblio. See http://repo1.maven.org/maven2/ch/qos/logback/ The logback manual is already available: http://logback.qos.ch/manual/index.html I hope this helps, At 09:41 PM 2/22/2007, Tomek Korzeniewski wrote: >Hello Ceki! > >Thank you for the information regarding logback. I just have a question >with it's availability on Ibiblio. I'm a very active Maven2 user and I >could only find v 0.3. Can you give an estimate when it will become >available on Ibiblio. Another question - are there any plans for a Logback >manual like the log4J one? > >Regards >Tomek. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

support for jdk 1.4?
by Keith 21 Feb '07

21 Feb '07

Hi: I've just received an email from Ceki about logback. It really looks interesting. However, the requirement for JDK 1.5 would prevent me from using logback as the logging mechanism because we are running WebSphere 6.0 which is based on JDK 1.4.2 Any plan on supporting JDK 1.4? Thanks, Keith

2 1

Re: [logback-user] LoggerFactory question
by Ceki Gülcü 09 Feb '07

09 Feb '07

At 07:04 PM 2/9/2007, Eric Crahen wrote: >I'm using Logback, but I build my code only against the SLF4J api. One >thing that I found strange was that LoggerFactory is not actually part of >the SLF4J api. Correct. >This poses a challenge to me, because I will need to depend on some >arbitrary implementation of an SLF4J api (probably the nop one) in order >to build my code. Then at deployment time, I need to remove that >slf4j-noop dependency and swap in a different one. The reason this is >tricky for me is that the deployment process I use currently is >(compile-time dependencies + extra runtime dependencies). The style in >slf4j creates a ((compile-time dependencies - slf4j-nop) + runtime >dependencies). This process is part of a larger overarching system that my >organization happens to use, so bucking the trend isn't too fun - though >possible. > >Also, it seems like all these implementations of LoggerFactory are pretty >much identical. I think that these could be consolidated into a single >LoggerFactory in the slf4-api package. This package could make use of the >ServiceProvider mechanism thats present in Java 4 & 5 + standard in Java 6 >to load the underlying Logger implementations. What do you think? I could >probably contribute a patch that would demonstrate how this might work. Hi Eric, This issue came up previously and will continue to haunt us for the foreseeable future. I'd wouldn't be exaggerating if I said that I'd be very much interested in your contribution. I am CCing the slf4j-dev list as well. You might want to submit your proposal there instead. >- Eric -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

LoggerFactory question
by Eric Crahen 09 Feb '07

09 Feb '07

I'm using Logback, but I build my code only against the SLF4J api. One thing that I found strange was that LoggerFactory is not actually part of the SLF4J api. This poses a challenge to me, because I will need to depend on some arbitrary implementation of an SLF4J api (probably the nop one) in order to build my code. Then at deployment time, I need to remove that slf4j-noop dependency and swap in a different one. The reason this is tricky for me is that the deployment process I use currently is (compile-time dependencies + extra runtime dependencies). The style in slf4j creates a ((compile-time dependencies - slf4j-nop) + runtime dependencies). This process is part of a larger overarching system that my organization happens to use, so bucking the trend isn't too fun - though possible. Also, it seems like all these implementations of LoggerFactory are pretty much identical. I think that these could be consolidated into a single LoggerFactory in the slf4-api package. This package could make use of the ServiceProvider mechanism thats present in Java 4 & 5 + standard in Java 6 to load the underlying Logger implementations. What do you think? I could probably contribute a patch that would demonstrate how this might work. -- - Eric

1 0

RE: [logback-user] add property for specifying logback.xmlfilelocation
by Ceki Gülcü 08 Feb '07

08 Feb '07

At 09:11 PM 2/8/2007, Newcomb, Michael-P57487 wrote: >Well, > >IMHO, a file that includes other files would not be simpler. > >It seems much simpler to for me to create 3 bat/sh files that do: > >foo-trace.bat: >java -Dch.qos.logback.config=foo/bar/logback-trace.xml Foo > >foo-debug.bat: >java -Dch.qos.logback.config=foo/bar/logback-debug.xml Foo > >foo.bat: >java Foo > >I might be misunderstanding your file inclusion idea. The file inclusion feature combined with system properties accomplishes the same thing as your original request. Let the contents of "logback.xml" be: <configuration> <include url="${logback-config}"/> </configuration> By setting the logback-config system property to a value of your choice, you could determine the config file that gets read. This approach yields the same results as your proposal except that we would not need to touch the initialization code. (It's already complicated as it is.) Does this make better sense? >Is Joran a part of Logback? If so, it introduces a dependency on Logback, >which using slf4j is supposed to alleviate. Joran ships within logback-core. As such, I couldn't quite parse your comment about SLF4J. :-) >For some background, I am developing a project (www.sf.net/projects/ohla) >that has both a library (for clients) and an executable (server). Best wishes for the ohla project. >Thanks, >Michael -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

RE: [logback-user] add property for specifying logback.xmlfilelocation
by Gerweck Andy - agerwe 08 Feb '07

08 Feb '07

I'm another happy, impressed LOGBack user who has very similar needs. Where I develop, we have several different deployment levels, all of which require substantially different logging configurations (e.g., development, qa, staging, production). However, our standard rollout procedure currently produces one standard build, as a zip file, for QA and above. We control the configuration in our startup with a few environment variables. As I start to push for my team's adoption of LOGBack, some mechanism like the one proposed below will be essential. I can't see any reason why I couldn't include a base logging configuration file in the classpath as a springboard to the configurable logging location. It would be convenient to specify the location for quick-and-dirty hacks, but I could live without it. The only drawback is that Log4j offers this, so there may be some in my group who protest changing to an implementation they may call “incomplete.” That said, if I could only have one, it would definitely be the inclusion mechanism. I’m not yet familiar with Joran, but it would be great if we could include some configure kind of mapping that along the lines of the below (pidgin pseudocode, but I think it's pretty clear). logName = case ENV{'env'} of 'qa' -> 'qa-logback.xml' 'dev' -> 'log-dev.xml' 'prod' -> 'logback.xml' logLocation = concat(ENV{'root'}, '/config/', logName) As long as I can control the location of the file with an environment variable, I can make things work, but it would be great to make the file location a function of one or more variables as above. Thank you, Andy Gerweck -----Original Message----- From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of Ceki Gülcü Sent: Thursday, February 08, 2007 11:51 AM To: logback users list Subject: RE: [logback-user] add property for specifying logback.xmlfilelocation Hi Michael, What you propose makes sense. However, I'd like to limit the number of ways logback can be configured (to ease the brain-footprint of logback on our users.) How about if we allowed a config file to include parts from a different sources? This inclusion feature should allow you to reference a different file. Moreover, since Joran supports variable substitution, you could set the value of the variable through a system property. You would get the feature you are asking for, and we would keep the initialization procedure simple (err, simpler.). WDYT? If you agree, could you please file a bug report asking for inclusion feature in joran/logback? At 07:08 PM 2/8/2007, Newcomb, Michael-P57487 wrote: >If I have multiple tests that measure performance, debugging, vs. ??? I >don't want to change the file or have duplicate files in different directories. > >Look at the logback examples directory. >logback-0.9\logback-examples\src\main\java\chapter2\ > >There are 3 different configuration files. I don't want any code >dependencies on Logback so the only way to configure logback is to use a >file called logback.xml or logback-test.xml. > >To execute chapter 2 I would have to copy those files to logback.xml or >logback-test.xml. Or put them in different directories and rename them all >to the same file name. > >Thanks, >Michael > >-----Original Message----- >From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On >Behalf Of Sebastien Pennec >Sent: Thursday, February 08, 2007 12:36 PM >To: logback users list >Subject: Re: [logback-user] add property for specifying logback.xml >filelocation > >Hello Michael, > >At the moment, logback can load two different files: logback.xml and >logback-test.xml. They need to be in the classpath and can be useful to >separate the environments, e.g. development and production. > >This behavior is usually enough for many situations. > >Can you precise your request with a use case that would need a java >variable and would not be possible with the actual behavior? > >Thanks, > >Sébastien > > >Newcomb, Michael-P57487 wrote: > > e.g.: > > -Dch.qos.logback.config=foo/bar/my-logback.xml > > > > Thanks, > > Michael > > > > > > ---------------------------------------------------------------------- > > -- > > > > _______________________________________________ > > Logback-user mailing list > > Logback-user(a)qos.ch > > http://qos.ch/mailman/listinfo/logback-user > >-- >Sébastien Pennec >sebastien(a)qos.ch > >Logback: The reliable, generic, fast and flexible logging framework for Java. >http://logback.qos.ch/ >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ****************************************************************************

1 0

RE: [logback-user] add property for specifying logback.xml filelocation
by Ceki Gülcü 08 Feb '07

08 Feb '07

Hi Michael, What you propose makes sense. However, I'd like to limit the number of ways logback can be configured (to ease the brain-footprint of logback on our users.) How about if we allowed a config file to include parts from a different sources? This inclusion feature should allow you to reference a different file. Moreover, since Joran supports variable substitution, you could set the value of the variable through a system property. You would get the feature you are asking for, and we would keep the initialization procedure simple (err, simpler.). WDYT? If you agree, could you please file a bug report asking for inclusion feature in joran/logback? At 07:08 PM 2/8/2007, Newcomb, Michael-P57487 wrote: >If I have multiple tests that measure performance, debugging, vs. ??? I >don't want to change the file or have duplicate files in different directories. > >Look at the logback examples directory. >logback-0.9\logback-examples\src\main\java\chapter2\ > >There are 3 different configuration files. I don't want any code >dependencies on Logback so the only way to configure logback is to use a >file called logback.xml or logback-test.xml. > >To execute chapter 2 I would have to copy those files to logback.xml or >logback-test.xml. Or put them in different directories and rename them all >to the same file name. > >Thanks, >Michael > >-----Original Message----- >From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On >Behalf Of Sebastien Pennec >Sent: Thursday, February 08, 2007 12:36 PM >To: logback users list >Subject: Re: [logback-user] add property for specifying logback.xml >filelocation > >Hello Michael, > >At the moment, logback can load two different files: logback.xml and >logback-test.xml. They need to be in the classpath and can be useful to >separate the environments, e.g. development and production. > >This behavior is usually enough for many situations. > >Can you precise your request with a use case that would need a java >variable and would not be possible with the actual behavior? > >Thanks, > >Sébastien > > >Newcomb, Michael-P57487 wrote: > > e.g.: > > -Dch.qos.logback.config=foo/bar/my-logback.xml > > > > Thanks, > > Michael > > > > > > ---------------------------------------------------------------------- > > -- > > > > _______________________________________________ > > Logback-user mailing list > > Logback-user(a)qos.ch > > http://qos.ch/mailman/listinfo/logback-user > >-- >Sébastien Pennec >sebastien(a)qos.ch > >Logback: The reliable, generic, fast and flexible logging framework for Java. >http://logback.qos.ch/ >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

2 1