February 2014 - logback-user

Re: [logback-user] Logback suddenly stopped logging
by Andreas Dejung 19 Jun '14

19 Jun '14

I had the same problem and I think I know why J Solaris does interrupt IO blocked thread which then causes the OutputStreamAppender to catch the IOException in line 218 (version 0.9.24). I actually run version 0.9.18 but this part has not change so I guess it will behave the same way. If we look at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4385444 InterruptedIOException should not be required by platform specification (sol) And log4j https://issues.apache.org/bugzilla/show_bug.cgi?id=44157 InterruptedIOException ignored by log4j I think it should be solved the same why } catch (InterruptedIOException iioe){ //give the thread a changes to act on interruption and then carry on Thread.currentThread().interrupt(); } catch (IOException ioe) { // as soon as an exception occurs, move to non-started state // and add a single ErrorStatus to the SM. this.started = false; addStatus(new ErrorStatus("IO failure in appender", this, ioe)); } I could not find the jira entry mentioned in this thread therefore I write it here J BTY the jvm option -XX:-UseVMInterruptibleIO does prevent the interruption by solaris but that's only a workaround and not solving the problem ;) Cheers Andy

8 16

Re: [logback-user] Add header-lines to each log file
by Schoeftner, Thomas 20 May '14

20 May '14

Sorry to bump this topic again. Any ideas? Thanks, -Tom

3 2

Maven Repository cannot resolve logback extensions
by Fritz, Jonathan 25 Feb '14

25 Feb '14

Upon adding the following to my pom.xml: <dependency> <groupId>org.logback-extensions</groupId> <artifactId>logback-ext-loggly</artifactId> <version>version</version> <scope>runtime</scope> </dependency> <dependency> <groupId>ch.qos.logback.contrib</groupId> <artifactId>logback-json-classic</artifactId> <version>version</version> <scope>runtime</scope> </dependency> <dependency> <groupId>ch.qos.logback.contrib</groupId> <artifactId>logback-jackson</artifactId> <version>version</version> <scope>runtime</scope> </dependency> I got this error while running mvn clean install: Failed to execute goal on project webapp: Could not resolve dependencies for project webapp:webapp:war:0.1-SNAPSHOT: The following artifacts could not be resolved: org.logback-extensions:logback-ext-loggly:jar:version, ch.qos.logback.contrib:logback-json-classic:jar:version, ch.qos.logback.contrib:logback-jackson:jar:version: Could not find artifact org.logback-extensions:logback-ext-loggly:jar:version in labs-consol-release (http://labs.consol.de/maven/repository) -> [Help 1] Seems like there might be a problem with the maven repository. Has anybody seen similar issues?

2 4

Repost: ReconfigureOnChangeFilter does not reuse context properties?
by Mike Müller 19 Feb '14

19 Feb '14

Hi At the risk of beeing annoying, I repost my question - in our production environment this is really a problem: -----Original Message----- From: Logback-user [mailto:logback-user-bounces@qos.ch] On Behalf Of Mike Müller Sent: Thursday, January 09, 2014 10:00 AM To: 'logback-user(a)qos.ch' Subject: [logback-user] ReconfigureOnChangeFilter does not reuse context properties? Hi I'm using a config file wich looks like this: <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="60 seconds" > <appender name="cms" class="ch.qos.logback.core.FileAppender"> <file>${pathToLogs}mysign-cms.log</file> <Append>false</Append> <encoder> <pattern>%d %30.30t %-5p %45.45c - %m%n</pattern> </encoder> </appender> <appender name="R" class="ch.qos.logback.core.FileAppender"> <file>${pathToLogs}log.log</file> <Append>false</Append> <encoder> <pattern>%d %30.30t %-5p %45.45c - %m%n</pattern> </encoder> </appender> <logger name="ch.mysign" additivity="false" level="INFO"> <appender-ref ref="cms"/> </logger> <root level="WARN"> <appender-ref ref="R"/> </root> </configuration> The parameter ${pathToLogs} comes from the following code: LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext( context ); context.reset(); context.putProperty( "pathToLog", "my-path-to-the-external-logs" ); configurator.doConfigure("my-logback-config.xml" ); } catch ( JoranException je ) { System.out.println( je.getMessage() ); } If I change the config file, the property "pathToLog" gets lost. Is this the same issue as descibed in [1]? If yes, is it a problem to reuse the context or at least the properties of the old context? [1] http://jira.qos.ch/browse/LOGBACK-592 best regards Mike _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

NPE when extending RollingFileAppender
by Johny Johnson 13 Feb '14

13 Feb '14

Hi, I'm having some trouble getting my custom appender which extends RollingFileAppender working. I've got my logback config being read and can extend FileAppender w/o issues but when I switch over to RollingFileAppender, I get the following: java.lang.NullPointerException: null at ch.qos.logback.core.rolling.RollingFileAppender.getFile(RollingFileAppender.java:122) ~[org.apache.sling.commons.log:4.0.0] Here is my config: <appender name="CUSTOM" class="com.mypackage.logging.CustomLogAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>log.%d{yyyy-MM-dd}.log</fileNamePattern> </rollingPolicy> <prudent>true</prudent> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> The only method that I override is writeout() as I needed to handle some particular events. Did I missing something obvious in terms of configuration? Any help is appreciated. Thanks! Johny

3 4

Logs lost when rolling
by Germán Ferrari 11 Feb '14

11 Feb '14

Hello. I'm having some strange behaviour with ch.qos.logback.core.rolling.TimeBasedRollingPolicy. I have the same war file deployed in two servers, but in one of them the logs of the day are lost when rolling ... I'm rolling daily at midnight. The modification date of the files in the server with the problem (03:10) coincides with a maintenance job which restarts the webserver. Here is a summary of the files involved: Server where the error occurs: -rw-r--r-- 1 webservd webservd 142 Feb 8 03:10 file.2014-02-07.log -rw-r--r-- 1 webservd webservd 261 Feb 9 03:10 file.2014-02-08.log -rw-r--r-- 1 webservd webservd 2.5K Feb 10 03:10 file.2014-02-09.log -rw-r--r-- 1 webservd webservd 261 Feb 11 03:10 file.2014-02-10.log -rw-r--r-- 1 webservd webservd 1004K Feb 11 12:40 file.log Server where it works ok: -rw-r--r-- 1 webservd webservd 6.7M Feb 7 20:36 file.2014-02-07.log -rw-r--r-- 1 webservd webservd 41K Feb 8 12:10 file.2014-02-08.log -rw-r--r-- 1 webservd webservd 5.8M Feb 10 22:32 file.2014-02-10.log -rw-r--r-- 1 webservd webservd 2.1M Feb 11 12:43 file.log The size of the files should be in the order of the megabytes, but, in the server with the problem, it is in the order of bytes. The contents are just some messages that are written when the application is shutdown, but all the logs of the day are lost ... Any hints of what could be happening? Thank you. Regards, Germán

1 0

browsing dbappender logs
by Chris Cheshire 11 Feb '14

11 Feb '14

I've been using FileAppenders for aeons and want to move my apps (web and headless server apps) to use the DBAppender, but I can't figure out how to view them easily other than hand crafting queries, which is just not sustainable. I looked at the Lilith project and from what I can tell I have to tell my apps to send logs to it, rather than it reading logs already created. Is this correct? I can't add use Lilith to receive logs because I don't want it running all the time just to browse through once a week. What solutions are there for browsing logs stored via a DBAppender? Thanks Chris

1 0

converting from ILoggingEvent to Apache LoggingEvent
by Deepak Singh 11 Feb '14

11 Feb '14

HI All, I have started migrating to logback from log4j.I have encounter issue with a class which is a remote appender(a JMX Mbean). The problem is this class returns the collection of LoggingEvent to remote clients. We are not a position to change the remote clients in near future. Is there any way I can convert ILoggingEvent to LoggingEvent easily. thanks Regards Deepak Singh 1-2 Berner Street London ext : 1907

1 0

ch.qos.logback.classic.sift.GSiftingAppender not found in version 1.1.1
by Rice Yeh 06 Feb '14

06 Feb '14

Hi, just upgrade to version 1.1.1, but an error shows ch.qos.logback.classic.sift.GSiftingAppender not found. I am using groovy to configure logback. In the document, it is mentioned that since 1.0.12, groovy configuration for SiftingAppender is not supported. Then, what is the alternative for newer version?

2 2

Log file is created but it is empty
by Rice Yeh 06 Feb '14

06 Feb '14

I am using logback version 1.0.11 with the following configuration. The log file is created but it is empty. That is, no log messages are put into it? What is wrong with my configuration? appender("close-period", GSiftingAppender) { discriminator(MDCBasedDiscriminator) { key = "period" defaultValue = "unknown" } //timeout = "1 minutes" sift { appender("close-${period}", FileAppender) { file = "${logDir}/close-${period}.log" append = false layout(PatternLayout) { pattern = "%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg%n" } } } } logger("mlm.close_period", INFO, ["close-period"], false) the test code is @Test def testClosePeriod { import org.slf4j.MDC val logger = LoggerFactory.getLogger("mlm.close_period") MDC.put("period", "2014-02") logger.info("testClosePeriod is run") MDC.remove("period") }

1 0