February 2007 - logback-user

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

[newbie] marker usage
by Xavier Hanin 03 Feb '07

03 Feb '07

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

1 0