April 2014 - 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

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

Re: [logback-user] Logback-user Digest, Vol 31, Issue 15
by David Tkaczyk 30 Apr '14

30 Apr '14

Look at documentation for logger config. additivity = false... Or look for DuplicateMessageFilter... Or write your own filter. On Apr 30, 2014 6:00 AM, <logback-user-request(a)qos.ch> wrote: > Send Logback-user mailing list submissions to > logback-user(a)qos.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qos.ch/mailman/listinfo/logback-user > or, via email, send a message with subject or body 'help' to > logback-user-request(a)qos.ch > > You can reach the person managing the list at > logback-user-owner(a)qos.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Logback-user digest..." > > Today's Topics: > > 1. How to get a unique content rollingFileAppender? (hax0r(a)sina.com) > > > ---------- Forwarded message ---------- > From: <hax0r(a)sina.com> > To: "logback-user" <logback-user(a)qos.ch> > Cc: > Date: Wed, 30 Apr 2014 15:23:42 +0800 > Subject: [logback-user] How to get a unique content rollingFileAppender? > > I want such a rollingFileAppneder: > > Before appending new line to the current log file, the logger will check: > if there is any same line in the current log file, it will not write the > same content to the file. > > > I can not find such a file appender, so I want to customize it: > > > Firstly, I want to create a class extends the RollingFileAppneder, but I > find that the field which point to current file in RollingFileAppneder is > "friendly", I can not get the field in my own class. > > > There is an stupid option: I copy all the codes in the > RollingFileAppneder, and changed some logic in the append part. > > > Is there a elgant way to get such a unique content rollingFileAppender? > > > > > > _______________________________________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user >

1 0

How to get a unique content rollingFileAppender?
by hax0r＠sina.com 30 Apr '14

30 Apr '14

I want such a rollingFileAppneder:Before appending new line to the current log file, the logger will check: if there is any same line in the current log file, it will not write the same content to the file. I can not find such a file appender, so I want to customize it: Firstly, I want to create a class extends the RollingFileAppneder, but I find that the field which point to current file in RollingFileAppneder is "friendly", I can not get the field in my own class. There is an stupid option: I copy all the codes in the RollingFileAppneder, and changed some logic in the append part. Is there a elgant way to get such a unique content rollingFileAppender?

1 0

How does the custom ContextSelector work?
by Traktor Toni 28 Apr '14

28 Apr '14

I have posed this question on stackoverflow: http://stackoverflow.com/questions/23088466/what-is-the-point-of-logbacks-c… Unfortunately with no replies. My question is essentially: How can I get a specific context by name if there is no ".getContext(name)" method? Isn't that the point of the whole custom context selection mechanism? But on what grounds can I select a context if I can't pass a string (or anything else) to ".getContext()"? Thank you for your help in advance.

1 0

NoSuchProviderException for smtp when using JavaMail 1.5.x with logback 1.1.2 SMTPAppender in glassfish 4
by Ross Goldberg 23 Apr '14

23 Apr '14

I am attempting to use the SMTPAppender from logback 1.1.2 in glassfish 4 to send email alerts for all logged errors, whether they are logged by glassfish itself, by its various components / modules / libraries, or by my code in a deployed ear. At different times, I tried using either JavaMail 1.5.0 or 1.5.1; 1.5.0 because glassfish 4 includes JavaMail 1.5.0 in its modules directory. and I wanted to try to be consistent; and 1.5.1 because it is the current version of JavaMail. I have configured the SMTPAppender, but when it tries to log an error from code deployed in my ear, I get a NoSuchProviderException for smtp when logback SMTPAppenderBase calls Transport.send(MimeMessage). This seems to be a ClassLoader issue, but I'm not well versed in ClassLoaders, especially with their use in glassfish, JavaMail, or logback. In the ${GLASSFISH_HOME}/glassfish/domains/domain1/config directory, I have placed: logback.xml (my logback config file) As I read online somewhere (I forget where), I placed the following files in the ${GLASSFISH_HOME}/glassfish/lib/endorsed directory: logback-core-1.1.2.jar logback-classic-1.1.2.jar jul-to-slf4j-1.7.7.jar (to redirect glassfish's built-in java.util.logging to logback) slf4j-api-1.7.7.jar (the logging api used log to logback) guava-16.0.1.jar (used by my custom logback logging code) custom-logging.jar (my custom logback logging code) javax.mail-1.5.0.jar logback SMTPAppender configuration fails without including javax.mail-1.5.0.jar in lib/endorsed, or, alternately, mailapi-1.5.0.jar. Using javax.mail-api-1.5.0.jar instead results in numerous errors in logback configuration, so that is not an option. If I use mailapi-1.5.0.jar without smtp-1.5.0.jar instead of using javax.mail-1.5.0.jar, SMTPAppenderBase throws a NoSuchProviderException when attempting to email glassfish errors (these are not errors from my ear, but errors from outside my ear). If I use javax.mail-1.5.0.jar, SMTPAppenderBase emails glassfish errors perfectly fine. I have tried various permutations of included JavaMail & logback jars the WEB-INF/lib directory in the war in my ear, but I keep getting NoSuchProviderExceptions when attempting to email errors that where logged by code from my ear. The only other JavaMail-related jars that I've found are in the glassfish modules directory; I cannot remove them since (from what I've heard) they are an integral part of glassfish. If I run a simple test java main method outside of glassfish, with the aforementioned jars in the classpath, error emails are sent correctly, without any exceptions. Any help resolving this issue would be greatly appreciated. Thanks.

1 0

Lilith 0.9.44 has been released!
by Jörn Huxhorn 21 Apr '14

21 Apr '14

This release brings huge improvements to the usage of conditions. Take a look at "Focus" and "Exclude" in the popup and "Search" menu. Remember that you can save conditions using Cmd/Ctrl-I. Those will show up in the "Saved conditions" section of "Focus" and "Exclude". It will also most likely be the last Java 5 compatible version. Development will continue on Java 8. Changes: - The table of the view will now always receive the focus if the selected view changes. - Added alternative behavior for Focus/Exclude actions. By default, those actions are replacing the current views filter, if available, with the new combined filter. Hold shift to create a new view instead. - Status text is now properly updated in case of a replaced filter. - Renamed "Named" in the find combo to "Saved". - Renamed "Add condition..." to "Save condition..." and moved it from the "View" to the "Search" menu. Also added it to the popup menu. - Significantly enhanced tooltips of various condition-related components. They now show a pretty-printed string representation of the condition. - Enhanced "Focus" and "Exclude" popup menus. - Added corresponding "Focus" and "Exclude" menus to the "Search" menu. - Added two Substance look&feels to the mix. - Status text of main window is now properly updated on change of white/blacklisted list name. - Enhanced profiling output of TracingAspect. - Fixed of-by-one error in message renderer [+x lines]. Again. - servlet-api dependency of de.huxhorn.lilith.logback.servlet is now "provided". - Added "Paste StackTraceElement" (Cmd-shift V) which opens the respective source code in the IDE, if a proper plugin is installed. - ClassicLilithEncoder is now Encoder<ILoggingEvent> instead of Encoder<LoggingEvent>. - Fixed suppressed handling while parsing Throwables. This is also a partial workaround for LOGBACK-328. - Added fishing-for-compliments technology. - Groovy 2.2.2, Logback 1.1.2, SLF4J 1.7.7, Jackson 2.3.3, log4j2 2.0-beta9, rrd4j 2.2, aspectj 1.8.0, flying-saucer 9.0.4, Spring 4.0.2, macify 1.6, httpcore 4.3.2, httpclient 4.3.3, JCommander 1.35, servlet-api 3.0.1, jgoodies-looks 2.5.3, commons-lang3 3.3.2 Known Issues: - Lilith is built with log4j2 2.0-beta9 and won't work with log4j2 2.0-rc1. The reason for this is that SocketAppender isn't working properly in that version. See LOG4J2-542. - HTML tooltips are not working with the native Mac OS X menu bar so some tooltips, especially the nice condition tooltips, will look garbled. Use a different look&feel to circumvent this problem. Unfortunately, I can't do anything about it. - Flying Saucer related issues: - Selection in the HTML view is currently somewhat buggy, especially in case of scaled view. - The first line of the message in HTML view is not properly indented if it starts with whitespace. You can see this effect by examining the event created by LogPinupLargeRunnable (executed via "Log ASCII"). The HTML created is actually correct. - Jumping to anchors is currently not supported so the navigation in help and details view isn't as good as it could be. - Lilith may hang during startup while creating the preferences dialog. Just restart Lilith in that rare case. This is caused by Java bug #6995182 and I can't do anything about it. Sorry about it. It's a stupid Java-MediaTracker-ColorChooser-Bug with no workaround available. m( ----------------------------------------------------------------------------- bitcoin: 19UjvmrDJMBcGDYQoFcrjYPqLRFPSwznZn litecoin: LU6WM3nmGJy3N5PEE8yQwsAyenJs8dtbmV dogecoin: DJC1R683hfD4VSEDAJrvNpv6GsCg8ewvhm

1 0

How to control WebApp logging by Tomcat control files
by Ulrich 21 Apr '14

21 Apr '14

Being new to WebApps, I started with TOMCAT 7 and try to do Logging with LOGBACK. I'm doing this already on WebApp Basis by adding all necessary resources to the WebApp Environment (WEB-INF). Here I'm using the ConsoleAppender and all messages are captured then by the default java.util.logging and stored to a file (just TOMCAT 7 default configuration). I found the explanation to replace java.util.logging by logback (http://logback.qos.ch/access.html) and got it running. But don't understand how it works. 1. I tried the sample configuration "Example 2: RollingFileAppender" but am still wondering where it's stored. Though the StatusMessageServlet displays some messages, I can't figure out from where they are retrieved. Only specifying <file>${catalina.base}/logs/access.log</file> directed the file to a known location. 2. The access.log was not zipped as indicated by the definition "<fileNamePattern>/access.%d{yyyy-MM-dd}.log.zip</fileNamePattern>" nor did it contain the messages displayed by the StatusMessageServlet 3. I've no clue how to control the WebApp logging by the central configuration file. I would prefer controlling logging be central config files rather than be files maintained by the WebApp itself. How can I manage to connect my WebApp to the central logback.xml I hope the questions make any sense. I'm lacking some fundamental understanding with logging by Tomcat. -- View this message in context: http://logback.10977.n7.nabble.com/How-to-control-WebApp-logging-by-Tomcat-… Sent from the Users mailing list archive at Nabble.com.

2 2

Disable scanning of logback.xml during initialization
by Simon Wong 17 Apr '14

17 Apr '14

Hi, I am using logback with Spring logback extension. The exact log location is determined at runtime through the "webAppRootKey" context param, that mentioned in WebLogbackConfigurer In web.xml, <context-param> <param-name>webAppRootKey</param-name> <param-value>myApp.root</param-value> </context-param> In logback.xml, <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${myApp.root}/../../logs/${FILE_NAME_PREFIX}.%d.log.zip</FileNamePattern> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{32} - %msg%n</pattern> </encoder> </appender> The issue is during logback initialization, it will scan the logback.xml automatically but the ${myApp.root} is not yet resolved, due to Spring Web Application Context is initialized lazily. The log entry could not write to log file successfully. The workaround solution is the program "touch" the logback.xml again during @PostConstruct phase after Spring Web Application Context is constructed. Logback will scan the change of logback.xml some time later and at that time the ${myApp.root} is correctly resolved. e.g. @PostConstruct void init() { try { ClassPathResource logbackResource = new ClassPathResource(logback.xml); File logbackConfigFile = logbackResource.getFile(); FileUtils.touch(logbackConfigFile); } catch (IOException ioe) { throw new RuntimeException(ioe); } } Is there a way that I could disable the auto scanning of logback.xml during initialization? Or defer until ch.qos.logback.ext.spring.web.LogbackConfigListener is well configured?

1 0

using JDK 1.6 in logback
by Ceki Gulcu 16 Apr '14

16 Apr '14

Hi All, Given that logback already requires JDK 1.6 to compile, and the recent release of Java 8, and that JDK 1.5 is no longer supported by Sun/Oracle, I think it's about time we move to JDK 1.6 for logback. Any objections or comments? Many thanks for your input. -- Ceki

5 5