March 2012 - logback-user - mailman3.qos.ch

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

(Important) Dynamically change the scan period
by Yihya Hugirat 08 Apr '13

08 Apr '13

hi all, i have migrated to logback to be able to change the log levels dynamically. i'm testing it now with calssfish 3.01 and somehow it is not working when i change the levels in logback.xml there nothing happens. by deploying from netbeans i get the following: |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@11bfee0 - Will scan for changes in [[C:\Dokumente und Einstellungen\user_Home\Eigene Dateien\NetBeansProjects\WS-LDAP\build\web\WEB-INF\classes\logback.xml]] every 15 seconds. but when i change the levels in this file nothing happens Any help will be appreciated Hugirat -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

3 4

Websphere specific JMX configuration?
by Sumanth Donthi 12 Jun '12

12 Jun '12

How can we enable JMX for logback in WebSphere ? Currently do not see ch.qos.logback.classic.jmx.Configurator in jconsole though <jmxConfigurator/> tag exist in logback configuration file. logback 0.9.27 WebSphere 7.0 This is similar to one posted earlier -- http://www.qos.ch/pipermail/logback-user/2010-November/001886.html -Sumanth

4 6

Replacing JUL with logback with Tomcat
by Alex Glass 31 May '12

31 May '12

I have setup logback-access according to the documentation with a LogbackValve and my Tomcat instance is logging requests. However it seems Tomcat is still writing messages to the console using JUL. What is the best way to route these messages to logback? Do I configure Tomcat to use log4j and then try and bridge those messages into logback-classic or is there a less complicated way? In the past I followed these instructions [1] to get Tomcat logging with log4j but would rather just use logback going forward. Thanks, Alex http://mrhaki.blogspot.com/2011/02/configure-log4j-on-tomcat.html

4 9

Re: [logback-user] syslogappender stacktraces get cut
by Ingebrigt Berg 15 May '12

15 May '12

Hi ! We have looked more into this issue. >From a TCPdump for the traffic between the app (using logback) and the syslog-server we learn that each line in the stacktrace is actually sent as a separate message to syslog (sensitive info replaced with xx/yy/zz): 11:28:37.911604 IP xx localhost.localdomain.55934 > localhost.localdomain.syslog: [bad udp cksum af4f!] SYSLOG, length: 101 Facility local3 (19), Severity error (3) Msg: Mar 30 11:28:37 yy2-31 zz-mce-test 30.03.2012 11:28:37.910 [ERROR] [LogbackTester] []: Fjas\0x0a 11:28:37.912028 IP xx localhost.localdomain.55934 > localhost.localdomain.syslog: [bad udp cksum 6076!] SYSLOG, length: 104 Facility local3 (19), Severity error (3) Msg: Mar 30 11:28:37 yy2-31 \0x09at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) The first packet is a regular log statement, the second one is a line in a stack trace. Notice how 'zz-mce-test 30.03.2012 11:28:37.910 [ERROR] [LogbackTester] []:' is replaced with: '\0x09at' If we interpret this correctly, SyslogAppender will log the error message and each StackTraceElement separately. But for the StackTraceElements it will ignore what we configure in the <SuffixPattern> property: ( <SuffixPattern>%contextName %d{dd.MM.yyyy HH:mm:ss.SSS} [%p] [%c{1}] [%X{ThreadId}]: %m%n</SuffixPattern> ) Instead the stackline messages simply get a '\0x09at' (a TAB) appended in place of the SuffixPattern. This happens in line 89 in ch.qos.logback.classic.net.SyslogAppender: sb.append(prefix).append(CoreConstants.TAB).append(step); Contrast that to line 59 in ch.qos.logback.classic.net.SyslogAppender (normal messages), where the SuffixPattern gets added: fullLayout.setPattern(prefixPattern + suffixPattern); We see two viable solutions: EITHER: when a message is split into a main message and StackTraceElements, the StackTraceElement messages must also get the content of the <SuffixPattern> appended OR: an optional property <StackTraceSuffixPattern> could be added to SyslogAppender, allowing control of what goes into StackTraceElement messages. cheers, Ingebrigt Berg + Marius Eikenes Den 11:40 20. mars 2012 skrev Ingebrigt Berg <ingebrigt(a)jpro.no> følgende: > Hi ! > > We've recently made the switch from Log4j to Logback. We use Syslog to > send logfiles to our logserver, and things generally work. > > But when there are stacktraces in the logs we get in trouble. > SyslogAppender will replace lineshifts with '#011' to make the logentry a > single line. Then it will cut each line that is to long according to the > syslog limit of 2K/line. Only the fist segment will arrive in the correct > log. The remaining segments are not prefixed with everything in the > suffixPattern, and our regexp will not have anything to match. The segment > will end up in a 'trash' log for unmatchable loglines. > > My config for the SyslogAppender looks like this: > > <contextName>company-${CONTEXT_PATH}-${environment}</contextName> > <appender name="LOGSERVER_FILE" > class="ch.qos.logback.classic.net.SyslogAppender"> > <syslogHost>localhost</syslogHost> > <facility>local3</facility> > <SuffixPattern>%contextName %d{dd.MM.yyyy HH:mm:ss.SSS} [%p] > [%c{1}] [%X{ThreadId}]: %m%n</SuffixPattern> > </appender> > > We use the contextName property to control the logfilename. On the > receiving end we read the contextName parameter (using a regexp) for each > log line, and write the line to a file with a corresponding name. > > We had a similar problem when we used Log4J (Where the Tag element was > used in the same manner), and fixed it back then by writing a custom log4j > SyslogAppender. But the main purpose of moving to Logback is to loose all > our home brew logging stuff, we don't want to go down that path again. If > we can't make Logback work out of the box with Syslog we'll probably end up > going back to Log4J. (Another alternative is to replace Syslog with Gelf, > but that's further down the road). > > However, I imagine Logback and Syslog being a common combination, and > surely someone must have this working out of the box. Any advice will be > appreciated. My requirements are simple: > -must work with no custom logging code, only config (preferably xml) > -stacktraces in logs must work > -must be able to fully control the filename on the recieving end. > > cheers, > Ingebrigt Berg >

2 7

SMTPAppender mail not sent (logback 1.0.0, JDK 1.5)
by Louis-Félix 03 May '12

03 May '12

Hi, I upgraded to logback 1.0.0 in a web application (tomcat 5, JDK 1.5), and the ERROR email are not sent anymore from the SMTPAppender. When I rollback my logback-core and logback-classic JARs to version 0.9.30, it's working again. I have a simple config: <appender name="courriel" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>smtp.xxx.xx.xx</smtpHost> <to>xxx(a)xxx.xx.xx</to> <from>no-reply.ti(a)xxx.xx.xx</from> <subject>Test</subject> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>25</bufferSize> </cyclicBufferTracker> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%date%level%thread%logger%line%message</pattern> </layout> </appender> I am using logback 1.0.0 with no problem in an other project (with JDK 1.6). Is there any known compatibility problem between logback 1.0.0 and JDK 1.5? Thanks, Louis-Félix

6 10

Configuring custom logback logger and appender in Spring beans
by Goyal 22 Mar '12

22 Mar '12

Hey, I am a newbie to logback.Please excuse me if my question is silly. I have a project which uses slf4j and log4j for some kind of logging. Now I want to have logback configured for some logging to files keeping along with the previous log4j and slf4j mechanisms. I am trying to configure spring beans for logback appender and logback logger in application context and then the logger beans are autowired with other beans (as property) which are already configured.. I am having problem in creating bean which will have resulting class ch.qos.logback.classic.Logger. Anybody having suggestions on how this can be done? Thanks in advance :-) -- View this message in context: http://old.nabble.com/Configuring-custom-logback-logger-and-appender-in-Spr… Sent from the Logback User mailing list archive at Nabble.com.

1 0

DBAppender with JNDI, JTDS
by Stein, Eric 21 Mar '12

21 Mar '12

I'm playing around with DBAppender, trying to get it to work with my webapp. What I'm finding is that this will log to the database: <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>net.sourceforge.jtds.jdbc.Driver</driverClass> <url>MY_URL</url> <user>MY_USERNAME</user> <password>MY_PASSWORD</password> </connectionSource> but this won't: <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> <param name="jndiLocation" value="jdbc/MyDatabase" /> </connectionSource> Username and password are set in the datasource definition. The specific error I'm getting is: 13:15:52,470 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@28:14 - RuntimeException in Action for tag [appender] java.lang.IllegalStateException: DBAppender cannot function if the JDBC driver does not support getGeneratedKeys method *and* without a specific SQL dialect at java.lang.IllegalStateException: DBAppender cannot function if the JDBC driver does not support getGeneratedKeys method *and* without a specific SQL dialect I read a little about SQLDialect, but I appear to be missing the part that shows how to configure it, and there's no dialect for JTDS. Am I up the creek here, or is this possible? Thanks, Eric _________________________________________________ Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com.

2 2

syslogappender stacktraces get cut
by Ingebrigt Berg 20 Mar '12

20 Mar '12

Hi ! We've recently made the switch from Log4j to Logback. We use Syslog to send logfiles to our logserver, and things generally work. But when there are stacktraces in the logs we get in trouble. SyslogAppender will replace lineshifts with '#011' to make the logentry a single line. Then it will cut each line that is to long according to the syslog limit of 2K/line. Only the fist segment will arrive in the correct log. The remaining segments do not contain everything in the suffixPattern, and our regexp will not have anything to match. The segment will end up in a 'trash' log for unmatchable loglines. My config for the SyslogAppender looks like this: <contextName>company-${CONTEXT_PATH}-${environment}</contextName> <appender name="LOGSERVER_FILE" class="ch.qos.logback.classic.net.SyslogAppender"> <syslogHost>localhost</syslogHost> <facility>local3</facility> <SuffixPattern>%contextName %d{dd.MM.yyyy HH:mm:ss.SSS} [%p] [%c{1}] [%X{ThreadId}]: %m%n</SuffixPattern> </appender> We use the contextName property to control the logfilename. On the receiving end we read the contextName parameter (using a regexp) for each log line, and write the line to a file with a corresponding name. We had a similar problem when we used Log4J (Where the Tag element was used in the same manner), and fixed it back then by writing a custom log4j SyslogAppender. But the main purpose of moving to Logback is to loose all our home brew logging stuff, we don't want to go down that path again. If we can't make Logback work out of the box with Syslog we'll probably end up going back to Log4J. (Another alternative is to replace Syslog with Gelf, but that's further down the road). However, I imagine Logback and Syslog being a common combination, and surely someone must have this working out of the box. Any advice will be appreciated. My requirements are simple: -must work with no custom logging code, only config (preferably xml) -stacktraces in logs must work -must be able to fully control the filename on the recieving end. cheers, Ingebrigt Berg

2 1

Appendere with timeBasedFileNamingAndTriggeringPolicy
by MarkIT 19 Mar '12

19 Mar '12

Hi everyone, I'm trying to create an appender with timeBasedFileNamingAndTriggeringPolicy but I got some trouble. I need to zip log files of previosly month in one .zip file (EX: on 04/01/2012 zip all file of March in one zip file). Here my logback.xml files: <configuration> <property scope="context" name="logFolder" value="log" /> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logFolder}/myLog.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${logFolder}/myLog.log-%d{yyyyMMdd}.%i.log.zip</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>2MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%d{dd-MM-yyyy HH:mm:ss:SSS} [%thread] %-5level %logger{35} - %msg%n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="ROLLING" /> </root> </configuration> Where I'm wrong? In this way, it zip file when log name change to MyLog_20120319_0.log Thanks in advance -- View this message in context: http://old.nabble.com/Appendere-with-timeBasedFileNamingAndTriggeringPolicy… Sent from the Logback User mailing list archive at Nabble.com.

1 0