- logback-user - mailman3.qos.ch

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

add property for specifying logback.xml file location
by Newcomb, Michael-P57487 08 Feb '07

08 Feb '07

e.g.: -Dch.qos.logback.config=foo/bar/my-logback.xml Thanks, Michael

2 2

Re: [logback-user] jul-bridge?
by Ceki Gülcü 07 Feb '07

07 Feb '07

At 07:13 PM 2/7/2007, Eric Crahen wrote: >You bet, ><http://bugzilla.slf4j.org/show_bug.cgi?id=38>http://bugzilla.slf4j.org/show_bug.cgi?id=38 Good, thanks. >Along similar lines, I wonder if it makes sense to move log4j-bridge up to >slf4j, or the jcl-bridge down into logback? Keeping all of the facade code >in one place. Funny you should mention it. Log4j-bridge used to be in SLF4J. However, since SLF4J does not have a notion of MDC, we had to migrate log4h-bridge into logback, where logback-classic includes an MDC class equivalent to log4j's MDC. As for jcl-over-slf4j, SLF4J is its natural home. As I said, the same is also true for log4j-bridge. Unfortunately, we couldn't get log4j-bridge to work as expected under the SLF4J roof. Cheers, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

Re: [logback-user] jul-bridge?
by Ceki Gülcü 07 Feb '07

07 Feb '07

At 05:08 PM 2/7/2007, Eric Crahen wrote: >Hi, > > I've been experimenting with logback + slf4j and have been quite > impressed. The slf4j API is what I write new code against, and I'm able > to leverage the jcl104-over-slf4j facade and logback-log4j-bridge to > intercept calls to commons logging and log4j respectively. This works > really well so far. I do have one other legacy logging API that is used > in some circumstances. That's the jdk14 jul api. Has anyone written a jul > Handler that will route jul calls to logback? Any comments on how well > that has/would work out? Many thanks. It's always a pleasure to hear good things about one's work. Except for bug#23 (see [1]) which is usually not blocking, the jcl104-over-slf4j bridge is known to work well for some time now. The logback-log4j-bridge is much more recent and works surprisingly well thus far. We currently use it in all our legacy systems in production. Although we have not attempted to do so, bridging the jul API should be possible. After all, x4juli does it. Would you mind creating a bug report so that we implement this feature for the next release of logback? [1] http://bugzilla.slf4j.org/show_bug.cgi?id=23 >Thanks, > >-- > >- Eric -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

2 1

jul-bridge?
by Eric Crahen 07 Feb '07

07 Feb '07

Hi, I've been experimenting with logback + slf4j and have been quite impressed. The slf4j API is what I write new code against, and I'm able to leverage the jcl104-over-slf4j facade and logback-log4j-bridge to intercept calls to commons logging and log4j respectively. This works really well so far. I do have one other legacy logging API that is used in some circumstances. That's the jdk14 jul api. Has anyone written a jul Handler that will route jul calls to logback? Any comments on how well that has/would work out? Thanks, -- - Eric

1 0

double logging
by Morgan Smith 05 Feb '07

05 Feb '07

Greetings, I am seeing double in the logging. Pretty standard config I think included below. Can't find any references to this problem. Wondering if anyone has encountered this. Example log output : 13161 [AnonymousIoService-1] DEBUG org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable - Exiting since queue is empty for /192.168.22.11:4001 13161 [AnonymousIoService-1] DEBUG org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable - Exiting since queue is empty for /192.168.22.11:4001 any help appreciated, -Morgan logback.properties : <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <appender name="bitranlog" class=" ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy "> <param name="FileNamePattern" value="bitran_%d{yyyy-MM}.log.gz" /> <param name="ActiveFileName" value="/var/log/smartcorridors/bitran.log" /> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <logger name="org.accma.concentrator.services.bitran.BiTranService"> <level value="debug"/> <appender-ref ref="bitranlog"/> </logger> <appender name="soccslog" class=" ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy "> <param name="FileNamePattern" value="soccs_%d{yyyy-MM}.log.gz" /> <param name="ActiveFileName" value="/var/log/smartcorridors/soccs.log" /> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <logger name="org.accma.concentrator.services.soccs.SOCCSService"> <level value="debug"/> <appender-ref ref="soccslog"/> </logger> <root> <level value="debug" /> <appender-ref ref="STDOUT" /> </root> </configuration>

2 1

Re: [logback-user] [newbie] marker usage
by Ceki Gülcü 04 Feb '07

04 Feb '07

Hi Xavier, Many thanks for your compliment. Would you care to create a bug report asking for an enhancement of the documentation as you describe in your email? You can do so under the logback-site/documentation heading [1]. The logback-demo [2] gives an example of how you could use markers. In a nut shell, you mark logging request with a marker and those marked request can be filtered accordingly. For example, assume you marked a request as "TRACE" as shown below: package ch.qos.logback.demo; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.slf4j.Marker; import org.slf4j.MarkerFactory; public class MarkerExample { static Marker TRACE_MARKER = MarkerFactory.getMarker("TRACE"); Logger logger = LoggerFactory.getLogger(MarkerExample .class); public void aMethod() { logger.info(TRACE_MARKER, "Hello world"); } } You can then instruct a turbo filter to drop requests marked with "TRACE" as follows: <turboFilter class="ch.qos.logback.classic.turbo.MarkerFilter"> <Name>TRACE</Name> <Marker>TRACE</Marker> <OnMatch>DENY</OnMatch> </turboFilter> Does the above help? [1] http://bugzilla.qos.ch/enter_bug.cgi?product=logback-site [2] http://logback.qos.ch/demo.html At 10:05 AM 2/3/2007, Xavier Hanin wrote: >Hi All, > >I'm new to logback, I've read a good part of the documentation, and first >I should said that I'm impressed by the quality of the documentation and >the feature rich logging system you provide. > >Two things: >Question: I have trouble to understand what is a Marker and what is the >use case behind them. Could you give me some insight? >Remark: While reading the documentation I had the feeling that MDC was >introduced too late. Indeed, you reference MDC the first time in chapter 2 >(as far as I can say), without giving even an hint on what it is. Several >other chapters reference this concept, but it's only in chapter 7 that I >understood what it is. Maybe adding a short introduction to this concept >(and the concept of Marker) in chapter 2 would help the reader? > >Thanks for your great work! > >Xavier >_______________________________________________ >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