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

jmxConfigurator.objectName property replacement
by Nico Serfontein 16 Mar '12

16 Mar '12

Hi, I'm trying this flag in logback.xml: '<jmxConfigurator objectName="user:type=ngp,name=logging,instance=${com.sun.aas.instanceName},context=DEM" />' But the instance in jconsole is '${com.sun.aas.instanceName}' and not my cluster's name. How can I get around this? Regards, Nico

2 2

logback performance issue
by Jason Tang 13 Mar '12

13 Mar '12

Hi We use logback for debug log, and find it has performance problem. Here is the environment and traffic information: Config: - RollingFileAppender - Default encoder Traffic - 60~100 concurrent threads write debug log parallel - each time, the logback will record a short message (eg, trace information, method in/out) - several hundreds record per thread per seconds, which means several ten thousand records per second total in one JVM. - Compress log every 20M After running our application, we found the performance is poor, and IO, CPU is not the bottle neck, but check the stack, all threads is waiting on the *OutputStreamAppender.*subAppend(). *Linux 2.6.32.27-0.2.2.2501.1.PTF-default 03/14/12 _x86_64_ * *avg-cpu: %user %nice %system %iowait %steal %idle 12.82 0.00 2.20 0.43 0.00 84.55 Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util sda 0.00 415.50 0.00 9.50 0.00 3400.00 357.89 0.27 28.21 7.37 7.00 * I searched, and find some previous discuss ( http://mailman.qos.ch/pipermail/logback-user/2011-March/002211.html) and it is same situation we have here, and the suggestion is to "vote back" the "ImmediateFlush" and "BufferSize". So I wonder if it is a performance problem? or Configuration fault? When I check the IO stat, I notice the io package is small, and it is same as the behavior in OutputStreamAppender. So if it is the existed problem or limitation, can we have the flush control and buffer size configuration back? Although we try to have the socketAppender and have our owner buffer solution when writer to file, but we need to find out what's the real problem. BRs //Jason

2 1

Lilith 0.9.42 has been released!
by Joern Huxhorn 12 Mar '12

12 Mar '12

Download it now at https://sourceforge.net/projects/lilith/files/lilith/0.9.42/ Lilith 0.9.42 - Release Notes Changes: - tail and cat are now fully supporting both LoggingEvent and AccessEvent. - Restored Logback SocketAppender in Lilith logging configuration. It's now triggered during debug actions, again. - Added support for new Java SE 7 try-with-resources statement suppressed Throwables. - After many runs that replace opened log file, Updating task failed with "Negative seek offset" - Added "Focus..." and "Exclude..." menus to popup. - "Edit", "Copy..." and "Filter..." menus are only enabled if it makes sense. - Added "Copy event as JSON" and "Copy event as XML". - Added lilith.timestamp.milliseconds system property. - Preventing multiple warning log-entries in case of broken groovy files (detailsView.groovy, Conditions, ClipboardFormatter). Instead, a warning is only emitted once for every file change. Instances aren't recreated in that case, either, so this also enhances the performance and lowers the CPU usage during general use. - Views are now properly updated upon preferences change. - Added option for "wrapped exception style" in details view. - Changed NDC to use varargs. - Added nottingham-draft HTTP status codes. - Relaxed namespace handling of all XML readers. This enables retrieval of old (1.3) Lilith XML Events. - All KeyStrokes are now managed globally. This includes validation of the used KeyStrokes which detected some mistakes: - "Close all tabs." is now Ctrl+Alt+Shift+W. - "Find previous active match" is now Ctrl+L. - "Find next active match" is now Ctrl+Shift+L. - "Copy Throwable" does now have the shortcut "command shift alt T". - SLF4J 1.6.4, Logback 1.0.1, Groovy 1.8.6, commons-lang 3.0.1, protobuf-java 2.4.1, jackson 1.9.2, jcommander 1.23, aspectj 1.6.11, cglib 2.2.2, httpclient 4.1.2, httpcore 4.1.3, commons-codec 1.5, JUnit 4.10, Spring 3.1.1.RELEASE Known Issues: - 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( Attention! This release changes detailsView.groovy in a way incompatible with previous versions! If you switch back to a previous version, you must reset this file. Simply execute "Preferences" => "Troubleshooting" => "Reinitialize details view files." in that case.

1 0

Using FileAppender to log within servlet not producing output
by Sotiris Delimanolis 12 Mar '12

12 Mar '12

Hi, I'm developing a Java web application through Tomcat with Java servlets. In my constructor for one servlet I call the following code: public MyServlet () { // Initialise the logger logger = (Logger)LoggerFactory.getLogger("application"); logger.debug("Starting application"); } My logback.xml configuration file is the following: <?xml version="1.0" encoding="UTF-8"?> <configuration debug="true"> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>application.log</file> <append>true</append> <encoder> <pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n </pattern> </encoder> </appender> <logger name="application" level="INFO"> <appender-ref ref="FILE" /> </logger> </configuration> When I launch the web app, the constructor is called by Tomcat, which should run the above code, but no file ("application.log") is created and no output is done anywhere. Within the same project, I try to test the Logger. In a junit test I have the following: public class TestLogging extends TestCase { public void testApplicationLogger() { // Initialise the logger Logger logger = (Logger)LoggerFactory.getLogger("application"); logger.error("Starting application"); } } This generates a file, a outputs "201 [main] ERROR application - Starting application" Why can't I get the logger to output anything from the servlet? Regards, Sotirios

2 4

SiftingAdapter TPS limit
by Yusuf Soysal 10 Mar '12

10 Mar '12

Hello, In logback manual logback.qos.ch/manual/mdc.html, it is written that "logback-classic assumes that values are placed into the MDC with moderate frequency". Can it handle 1000 requests per second? What is the TPS interval when we talk about "moderate frequency"?

2 1

Want a new log every time application starts
by Steve Cohen 08 Mar '12

08 Mar '12

I want a new log file to be created every time an application starts. I translate this wish into "roll the log upon the first log statement emitted by the application after it starts". It seemed pretty trivial to implement this but I can't get it to work. 1. I created a policy: ============================================================================== package com.whatever.logging; import java.io.File; import ch.qos.logback.core.rolling.TriggeringPolicyBase; /** * This policy causes a log to be rolled over with the first log statement * of every program run. */ public class LogPerRunTriggeringPolicy<E> extends TriggeringPolicyBase<E> { private static boolean rollMeOver = true; /* (non-Javadoc) * @see ch.qos.logback.core.rolling.TriggeringPolicy#isTriggeringEvent(java.io.File, java.lang.Object) */ @Override public boolean isTriggeringEvent(File activeFile, E event) { boolean rollStatus = rollMeOver; if (rollMeOver) { System.out.println("rollover will be triggered"); rollMeOver = false; } return rollStatus; } } ================================================================================= and an appender using that policy: <appender name="Conversation" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${logdir}/conversation.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>conversation.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>6</maxIndex> </rollingPolicy> <triggeringPolicy class="com.whatever.logging.LogPerRunTriggeringPolicy" /> <encoder> <pattern>%d [%t] %-5p %c{2} - %m%n</pattern> </encoder> </appender> ================================================================================= But the log never rolls. What am I doing wrong?

1 0

Release of logback version 1.0.1
by ceki 07 Mar '12

07 Mar '12

Hello all, I am happy to announce the release of logback version 1.0.1. It should hit the Maven central repository within the next 24 hours. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki http://twitter.com/#!/ceki

1 0

http://jira.qos.ch/browse/LBCLASSIC-221
by ceki 06 Mar '12

06 Mar '12

Hello Jacob, FYI, LBCLASSIC-221 was solved in a recent commit [1] to be released in version 1.0.1. The problem you describe is different than the one discussed in LBCLASSIC-221. Could you please file a separate bug report? I've also looked at your patch. However, let's discuss that within the new bug report. Cheers, [1] https://github.com/ceki/logback/commit/26a0a37c -- Ceki http://twitter.com/#!/ceki

1 0

use logback in OSGi (Felix and karaf)
by Rice Yeh 06 Mar '12

06 Mar '12

Hi, My programs are running in Apache Felix with karaf as console. I have changed karaf.sh to provide -Dlogback.configurationFile. In the configuration file, I have a file appender and console. When running, this file appender is created. However, no log recorder is generated either to the file or console. When using in OSGi, what more configuration I need to do? The 3 jars I am using are slf4j-api-1.6.4.jar, logback-core-1.0.0.jar, and logback-classic-1.0.0.jar. Rice

1 0

SMTP Appender silently fails
by Alex Glass 05 Mar '12

05 Mar '12

I'm trying to use SMTPAppender to send a log message through gmail. I have added javax.mail:mailapi:1.4.3 as a depdendency. I also tried adding javax.activation:activation:1.1.1 with no success. If I change the host to xyz, it has no affect. This is my configuration file: <configuration debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern> %-4relative [out] %-5level %logger - %msg%n </pattern> </encoder> </appender> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>smtp.gmail.com</smtpHost> <smtpPort>465</smtpPort> <SSL>true</SSL> <username>somebody(a)gmail.com</username> <password>somepass</password> <to>someone(a)gmail.com</to> <from>somebody(a)gmail.com</from> <subject>Testing %logger{20} - %m</subject> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{1} - %msg%n</pattern> </layout> </appender> <root level="info"> <appender-ref ref="STDOUT" /> <appender-ref ref="EMAIL" /> </root> </configuration> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Console output 12:45:56,627 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 12:45:56,630 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 12:45:56,644 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 12:45:56,668 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.net.SMTPAppender] 12:45:56,678 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [EMAIL] 12:45:56,714 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 12:45:56,714 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 12:45:56,715 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [EMAIL] to Logger[ROOT] 12:45:56,715 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 180 [out] INFO SmtpTest - Hello World

3 3