- logback-user - mailman3.qos.ch

Release of logback v0.9.24
by Ceki Gülcü 14 Oct '10

14 Oct '10

Hello all, I am happy to announce the release of logback version 0.9.25. Please refer to the news page for precise details. 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

2 1

Logback NPE in Felix OSGi container.
by Mark Protas 13 Oct '10

13 Oct '10

I'm hitting an NPE in logger initialization in the Felix OSGi container if I specify the logback.configurationFile system property. Without the system property, I don't hit this and everything logs to the ConsoleAppender as expected. Any suggestions as to how to fix this? java.lang.NullPointerException at ch.qos.logback.core.util.Loader.getResourceOccurenceCount(Loader.java:58) at ch.qos.logback.classic.util.ContextInitializer.multiplicityWarning(ContextInitializer.java:160) at ch.qos.logback.classic.util.ContextInitializer.statusOnResourceSearch(ContextInitializer.java:183) at ch.qos.logback.classic.util.ContextInitializer.findConfigFileURLFromSystemProperties(ContextInitializer.java:111) at ch.qos.logback.classic.util.ContextInitializer.findURLOfDefaultConfigurationFile(ContextInitializer.java:120) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:148) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at com.weiglewilczek.slf4s.Logger$.apply(logger.scala:32) at com.weiglewilczek.scalamodules.package$.<init>(package.scala:84) at com.weiglewilczek.scalamodules.package$.<clinit>(package.scala) at com.smiley.validation.create.Activator.start(Activator.scala:22) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:633) at org.apache.felix.framework.Felix.activateBundle(Felix.java:1822) at org.apache.felix.framework.Felix.startBundle(Felix.java:1739) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1143) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:637) CONFIDENTIALITY NOTICE: This e-mail message is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521 and, together with any attachments, is intended only for the addressee. If you are not the intended recipient of this message, you may not disclose, print, copy, or disseminate this information. If you have received this in error, please reply and notify the sender (only) and delete the message along with any attachments. Unauthorized interception of this email is a violation of federal criminal law. If your company has signed a confidentiality agreement with Smiley Media, the content of this email is designated 'Confidential Information' within the meaning of that agreement.

2 1

How to create log files per log level
by lunch716＠yahoo.co.jp 12 Oct '10

12 Oct '10

Hi, I'm using logback core and classic(both version are 0.9.9) with jdk5.0. My goal is to generate a log file per log level.Namely error.log is for error level and warn.log is for warn level and so on. I found the following thread though, http://marc.info/?l=logback-user&m=125052059800553&w=2 I could not create the LevelBasedDiscriminator class because I could not find the classes below on logback 0.9.9. ch.qos.logback.classic.sift.SiftingAppender ch.qos.logback.core.sift.Discriminator ch.qos.logback.classic.spi.ILoggingEvent I have two questions. Q1.Is it possible to create log files per log level? Q2.If I have to give up the use of SiftingAppender,how can I accomplish my goal? -------------------------------------- Learn more about breast cancer - Pink Ribbon Campaign 2010 http://yj.pn/JAy9L7

1 1

Separate log files for different threads
by Cyber Jack 11 Oct '10

11 Oct '10

Hello, I am wondering if it is possible to separate logging based on thread names? I would like logs generated by every thread to go into distinct log files, one log file per thread e.g FILE-${thread}.log. I know that I can have all threads write to a single log file and then grep on thread name, but want to know if there is a better approach. I have tried SiftingAppender and put the thread name into the MDC in each thread, but it didn't work. Thanks

2 1

Configuring JMSQueueAppender to send messages to a Websphere MQ server
by Espen Rydningen 11 Oct '10

11 Oct '10

Hi Has anyone successfully configured the JMSQueueAppender to send messages to a Websphere MQ server? I'm really struggling with this. Hope someone can assist. Here is my configuration file: logback-test.xml <?xml version="1.0" encoding="UTF-8" ?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern> %d{HH:mm:ss} [%thread] %-5level %logger{0} - %msg%n </pattern> </encoder> </appender> <appender name="QUEUE" class="com.foo.bar.common.log.CustomJMSQueueAppender"> <InitialContextFactoryName>org.apache.activemq.jndi.ActiveMQInitialContextFactory</InitialContextFactoryName> <ProviderURL>tcp://10.10.10.10:1414</ProviderURL> <QueueConnectionFactoryBindingName>ConnectionFactory</QueueConnectionFactoryBindingName> <QueueBindingName>app_test_log</QueueBindingName>  <filter class="com.foo.bar.common.log.MarkerFilter"> <marker>JMS</marker> <onMismatch>DENY</onMismatch> <onMatch>ACCEPT</onMatch> </filter> </appender> <root level="TRACE" > <appender-ref ref="STDOUT" /> <appender-ref ref="QUEUE" /> </root> </configuration> My MQ guy who sat up the queue gave me these values: qmanager is ESAPFOK9 machine is 10.10.10.10 Channel is app.logging queue is app_test_log These are the essential parts of my Maven2 pom file: <?xml version="1.0" encoding="UTF-8"?> (...) <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>0.9.21</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.8.1</version> <scope>test</scope> </dependency> <dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-core</artifactId> <version>5.0.0</version> <scope>test</scope> <exclusions> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> </exclusion> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging-api</artifactId> </exclusion> <exclusion> <groupId>org.apache.activemq</groupId> <artifactId>activeio-core</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </project> I made a really simple Junit test: public class CustomJMSQueueAppenderTest { private final static Logger logger = LoggerFactory.getLogger(CustomJMSQueueAppenderTest.class); private static Marker JMS_LOG = MarkerFactory.getMarker("JMS_LOG"); @Test public void sendLogMessageToMqAndFile(){ logger.info("New test run: {}", new Date()); logger.info("This message will only be sent to console"); logger.info(JMS_LOG, "This message is to be sent both to console and to JMS"); } } But alas, this was the result: Running com.foo.bar.common.log.CustomJMSQueueAppenderTest 15:50:41,860 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at [file:/usr/IBM/build/frontend-trunk/delegator/foobar/target/test-classes/logback-test.xml] 15:50:42,329 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 15:50:42,411 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 15:50:42,431 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 15:50:42,593 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [encoder] on top of the object stack. 15:50:42,872 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [filter] on top of the object stack. 15:50:42,961 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [com.foo.bar.common.log.CustomJMSQueueAppender] 15:50:42,981 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [QUEUE] 15:50:43,070 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [filter] on top of the object stack. 15:50:47,121 |-ERROR in com.foo.bar.common.log.CustomJMSQueueAppender[QUEUE] - Error while activating options for appender named [QUEUE]. javax.jms.JMSException: java.io.EOFException at javax.jms.JMSException: java.io.EOFException at at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49) at at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1178) at at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1262) at at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:292) at at org.apache.activemq.ActiveMQConnection.createQueueSession(ActiveMQConnection.java:1123) at at ch.qos.logback.classic.net.JMSQueueAppender.start(JMSQueueAppender.java:113) at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:60) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:121) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at java.lang.J9VMInternals.initializeImpl(Native Method) at at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at at com.foo.bar.common.log.CustomJMSQueueAppenderTest.<clinit>(CustomJMSQueueAppenderTest.java:13) at at java.lang.J9VMInternals.initializeImpl(Native Method) at at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) at at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at at java.lang.reflect.Constructor.newInstance(Constructor.java:522) at at org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:202) at at org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:251) at at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at at org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:248) at at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at at java.lang.reflect.Method.invoke(Method.java:618) at at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: java.io.EOFException at at java.io.DataInputStream.readFully(DataInputStream.java:204) at at java.io.DataInputStream.readInt(DataInputStream.java:380) at at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268) at at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192) at at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184) at at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172) at at java.lang.Thread.run(Thread.java:810) Now I'm very lost. Hoping someone can help me out. Best regards Espen

2 2

documentation for <pattern>
by Francisco Sanmartin 07 Oct '10

07 Oct '10

Hello Can anybody tell me where is the documentation for the tag<pattern> within an<encoder> ? I would like to know all the options available to configure the log style. For example, <encoder> <pattern>%d{HH:mm:ss.SSS} %-4relative %-5level %logger{35} - %msg%n</pattern> </encoder> I'd like to know what else can I configure there. Thanks in advance -- Met vriendelijke groet/Kind regards, Francisco Sanmartin Software developer PLEASE NOTE OUR NEW ADDRESS AND WEBSITE i-Optics BV Westeinde 12C 2512 HD Den Haag The Netherlands Tel: +31 (0)70-399 3112 Fax: +31 (0)70-415 5215 f.sanmartin(a)i-optics.com f.sanmartin(a)eyeprevent.nl Website: http://www.i-optics.com Website: http://www.eyeprevent.nl

1 1

log.callAppenders and DBAppender
by Jon Anderson 05 Oct '10

05 Oct '10

I'm using the JMSTopicAppender to log events from numerous applications and a MDB that consumes those messages and reissues the log statements just like the example JSMTopicSink application. The MDB side of things has a rolling file appender configured, as well as a DBAppender. When I issue standard log statements within the MDB, the log statements are both appearing in the DB tables and in the file. However, the log statements issued by the log.callAppenders() (IE, the event from the JMS message) are only appearing in the file, not the DB tables. In fact, when I trace the queries being executed, a start and stop transaction statement is being issued for each log event, but no insert is generated. I've assumed I have everything configured correctly, as log.info("Message") works, but log.callAppenders(event) doesn't. Is there some piece I am missing? Thanks, Jon

1 1

SiftingAppender question
by Gabor Dolla 04 Oct '10

04 Oct '10

Hi Is it possible to configure the SiftingAppender to use parameters from MDC other than the discriminator ? I'd like to achive the following : in java: MDC.put("logger", loggerName); MDC.put("file", fileName); MDC.put("pattern", pattern); in config: <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator> <Key>logger</Key> <DefaultValue>default</DefaultValue> </discriminator> <sift> <appender name="FILE-${logger}" class="ch.qos.logback.core.FileAppender"> <File>${file}</File> <Append>true</Append> <Encoding>UTF-8</Encoding> <BufferedIO>true</BufferedIO> <ImmediateFlush>true</ImmediateFlush> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>{pattern:-%d [%thread] %level %mdc %logger{35} - %msg%n}</Pattern> </layout> </appender> </sift> </appender> Thanks Gabor Dolla

2 4

Re: [logback-user] Appender Ref Default Value
by Pablo Lascano 04 Oct '10

04 Oct '10

Hello, is this issue solved? I'm using v0.9.24 and having the same problem... Thanks! -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl

2 1

linux AIO appender?
by Christian Schuhegger 03 Oct '10

03 Oct '10

Hello list, as described in the following link HornetQ uses some native code on linux to speed up their persistence operations: http://java.dzone.com/articles/hornetq-stings-competition I was wondering if a similar approach could also help to increase the performance of logging on linux systems? Did anybody already start to think in that direction? Independent of that I would be interested to know if there are some research results readily available that examine the impact of logging on the performance of Java applications? Many thanks, -- Christian Schuhegger http://www.el-chef.de/

1 0