December 2010 - logback-user

Issue with log files generation on MAC machines
by Nikhil Diwan 07 Dec '10

07 Dec '10

Hi, There seems issue with logback generating log files on MAC machines. Instead of loggers creating log folder/log files log messages are being displayed on console. logback.groovy:- import ch.qos.logback.classic.encoder.PatternLayoutEncoder import ch.qos.logback.core.FileAppender import ch.qos.logback.core.rolling.FixedWindowRollingPolicy import ch.qos.logback.core.rolling.RollingFileAppender import ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy import static ch.qos.logback.classic.Level.DEBUG def LOG_HOME = "/test/logback/logs" def filePatternFormat = "%d %-5level %logger - %msg%n" // Defining appender for root appender('FILE', FileAppender) { file = "${LOG_HOME}/root.log" encoder(PatternLayoutEncoder) { pattern = filePatternFormat } } appender("MACLogback", RollingFileAppender) { file = "${LOG_HOME}/MACLogback.log" rollingPolicy(FixedWindowRollingPolicy) { fileNamePattern = "MACLogback.%i.log.zip" minIndex = 1 maxIndex = 10 } triggeringPolicy(SizeBasedTriggeringPolicy) { maxFileSize = "10MB" } encoder(PatternLayoutEncoder) { pattern = filePatternFormat } } logger 'MACLogback', DEBUG, ['MACLogback'], false root DEBUG, ['FILE'] java file:- import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class MACLogback { public static void main(String[] args) { System.out.println("Before logging"); Logger logger = LoggerFactory.getLogger(MACLogback.class); logger.debug("THIS IS FOR TESTING LOGBACK CONFIGURATION ON MAC!"); System.out.println("After logging"); } } I see log statements on CONSOLE as : Before logging 11:07:24.309 [main] DEBUG MACLogback - THIS IS FOR TESTING LOGBACK CONFIGURATION ON MAC! After logging ISSUE: Log file is not created under "/test/logback/logs" location, which is expected. Any thoughts??

1 0

Access logs + SocketAppender + SimpleSocketServer
by Denis Bazhenov 06 Dec '10

06 Dec '10

I'm trying to use SimpleSocketServer (from logback-access) for remote logging of AccessEvent's. The problem I faced is following. When object get deserialized in SocketNode on line 64 it has no httpRequest (it's simply null). There is debugger dump of event: event = instance of ch.qos.logback.access.spi.AccessEvent(id=932) Thread-1[1] dump event event = { serialVersionUID: 866718993618836343 NA: "-" NA_STRING_ARRAY: instance of java.lang.String[1] (id=914) EMPTY: "" SENTINEL: -1 httpRequest: null httpResponse: null requestURI: "/" requestURL: "GET / HTTP/1.1" remoteHost: "192.168.20.179" remoteUser: null remoteAddr: "192.168.20.179" protocol: "HTTP/1.1" method: "GET" serverName: "jetty-test" requestContent: "" responseContent: "" requestHeaderMap: instance of java.util.TreeMap(id=938) requestParameterMap: instance of java.util.HashMap(id=939) responseHeaderMap: instance of java.util.HashMap(id=940) contentLength: 1288 statusCode: 503 localPort: 8080 serverAdapter: null timeStamp: 1291621192027 } So later this gives me NPE in AccessEvent.buildRequestHeaderMap(). Where I should look? Is this some serialization/deserialization problems?

2 2

rolling log files every x minutes or hours
by Nathaniel Auvil 05 Dec '10

05 Dec '10

I have a requirement to roll our log files at a configurable period which could be every 15 minutes, or every 2 hours. Does Logback support this (does not look like it). Would I have to implement a custom TriggerPolicy to do this? Anyone have any pointers? Seems something like this would be very useful to the framework.

1 0

Getting tomcat logs through Logback
by Pradnya Gawade 03 Dec '10

03 Dec '10

Hi, I want to get the tomcat logs through logback. I got following reference related to it and planning to try it, the only difference in my case would be a Syslog appender instead of a log file: http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j This approach required doing some changes in tomcat lib directory etc. I know Logback provides bridging to legacy APIs like java.util.logging http://www.slf4j.org/legacy.html I used jul-to-slf4j bridge to get the liquibase logs into my web application log file. Similarly does Logback provide some thing to get tomcat logs through logback. It is OK with me to get the copy of tomcat logs and tomcat also logging to to its own log files separately. Tomcat uses common logging internally. If I could get some way in which user don't have to make any changes in the tomcat configuration before/after the application deployment then it will be great. Any inputs? Thanks, Pradnya

2 3

Changing the log level on a per-message basis
by Jason R Briggs 03 Dec '10

03 Dec '10

Hi Is there a reason why LoggingEvent.setLogLevel is a one-shot process? I'm writing a converter which should be able to modify the level of the log message (based on config), however that won't work because the method will throw an illegal arg exception on subsequent access. Or is there a better way to do this? Thx, Jason

1 0

Dynamically attaching the loggers to appenders
by Pradnya Gawade 02 Dec '10

02 Dec '10

Hi, I am having the issue described below, sorry for the long post but I think that is required to better explain the problem. I want to separate out the logs in such a way that some special packages, classes needs to go in specific log format and rest of the logs will go in default format. I have created the multiple file, Syslog appenders with all the required formats. But I am having difficulty configuring in such a way that the log messages from packages other than my special packages will go with the default appender. Initially my idea was to map the basic outer package to all the special appenders as well as to default appender, create a filter for each special appender so it will only take the specific package logs only. But the problem is that default appender takes all the log messages. I can again implement a filter for the default appender so it will take all the excluded log s only but probably it it will be lot of processing unnecessarily, evaluating the same criteria again and again for each logging request. Is there any way so I can intercept each logging request such that I can decide which appender I need this logger to map to (by implementing some java routine), put the result in MDC context and make use of that result variable in the configuration to associate the required appender (using if-else syntax)? I saw that Sifting appender might be helpful in this scenario but I don't know where I can put my processing logic to decide which appender I want the logger to associate to so I can use its result as discrminator. Any ideas? Thanks, Pradnya

1 1