August 2010 - 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

Class not found exception for LoggingEventVO
by MDerr＠nycm.com 13 Jan '12

13 Jan '12

I have an application client set up to send a logging message over a bus using a logback JMSQueueAppender. Logback version is 0.9.24 and slf4j version is 1.6.1. This is running on a Websphere 7.0 server in Rational Application Developer 7.5. I've tested the bus and queue with a simple text message using the RAD Universal Test Client and that works fine, so at least the foundation is solid. When I log a message to the message queue, I wind up with the following stack trace under a wide variety of attempts: [8/11/10 14:44:16:223 EDT] 0000002b SystemOut O Exception CWSIA0122E: An exception occurred deserializing a message, exception: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.LoggingEventVO. [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R javax.jms.MessageFormatException: CWSIA0122E: An exception occurred deserializing a message, exception: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.LoggingEventVO. [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsObjectMessageImpl.getObject( JmsObjectMessageImpl.java:277) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.csg.logger.mdb.NYCMLoggerMDB.handleMessage(NYCMLoggerMDB.java:45) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.csg.logger.mdb.NYCMLoggerMDB.onMessage(NYCMLoggerMDB.java:36) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod( MessageEndpointHandler.java:1092) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ejs.container.MessageEndpointHandler.invoke( MessageEndpointHandler.java:777) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at $Proxy42.onMessage(Unknown Source) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint( JmsJcaEndpointInvokerImpl.java:233) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch( SibRaDispatcher.java:900) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run( SibRaSingleProcessListener.java:550) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R Caused by: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.LoggingEventVO [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.lang.Class.forNameImpl(Native Method) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.lang.Class.forName(Class.java:136) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.loadClass(WsObjectInputStream.java:227 ) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.access$000(WsObjectInputStream.java:53 ) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream$2.run(WsObjectInputStream.java:191) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.security.util.AccessController.doPrivileged( AccessController.java:118) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.resolveClass( WsObjectInputStream.java:164) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.resolveClass( WsObjectInputStream.java:156) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1591) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1512) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1748) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364) [8/11/10 14:44:16:239 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsObjectMessageImpl.getObjectInternal( JmsObjectMessageImpl.java:345) [8/11/10 14:44:16:239 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsObjectMessageImpl.getObject( JmsObjectMessageImpl.java:271) [8/11/10 14:44:16:239 EDT] 0000002b SystemErr R ... 10 more This always happens when trying to get the message object out of the message in the onMessage code in my message driven bean. For example, the stack dump was generated at the event = . . . line in the code below: if (msg instanceof ObjectMessage){ ObjectMessage objectMesssage = (ObjectMessage) msg; System.out.println("Got ObjectMessage"); event = (ILoggingEvent) objectMesssage.getObject(); } I have the logback classic jar on my classpath successfully because I use a number of other classes from it in my code. If anyone can help with this, I would appreciate it. I can provide additional information as needed. Thanks, Merritt Derr ***CONFIDENTIALITY NOTICE*** This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.

3 2

org.slf4j.impl.StaticLoggerBinder.SINGLETON
by Rusty Wright 25 Oct '11

25 Oct '11

I'm unable to create a bugzilla account at http://bugzilla.slf4j.org/createaccount.cgi Could someone enter this bug report for me? If I change my version of logback to 0.9.11 I don't get this. I get it when I use logback version 0.9.13. I'm using version 1.5.5 of slf4j. Thanks Running TestSuite org.apache.maven.surefire.booter.SurefireExecutionException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest; nested exception is org.testng.TestNGException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest org.testng.TestNGException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest at org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:35) at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:330) at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:62) at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:81) at org.testng.internal.TestNGClassFinder.<init>(TestNGClassFinder.java:114) at org.testng.TestRunner.initMethods(TestRunner.java:281) at org.testng.TestRunner.init(TestRunner.java:227) at org.testng.TestRunner.init(TestRunner.java:189) at org.testng.TestRunner.<init>(TestRunner.java:138) at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:477) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:244) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:821) at org.testng.TestNG.runSuitesLocally(TestNG.java:788) at org.testng.TestNG.run(TestNG.java:708) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:26) ... 23 more Caused by: java.lang.IllegalAccessError: tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory at org.slf4j.LoggerFactory.staticInitialize(LoggerFactory.java:83) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:73) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:272) at org.springframework.test.context.testng.AbstractTestNGSpringContextTests.<init>(AbstractTestNGSpringContextTests.java:77) at edu.berkeley.ist.cars.net.email.EmailTest.<init>(EmailTest.java:21) ... 28 more

4 5

use of java.io.File in logback / Android
by Robert Schmid 08 Jul '11

08 Jul '11

I am about to implement an appender that I can use on Android. I'm guessing it won't be much more difficult than doing the same from log4j. The primary problem is that we can't really use java.io.File to access the file system. Android has its own File access API. I believe that this will be as simple as extending RollingFileAppender and overriding methods as needed to swap out the File access apis. Can anybody spot the flaw in my thinking? Are there other pitfalls I need to worry about? Robert Schmid robertschmid(a)airstriptech.com<mailto:robertschmid@airstriptech.com> [cid:image001.jpg@01CB3406.9303A990] www.airstriptech.com<http://www.airstriptech.com/>

3 3

Are included files scanned
by Rosarin Jolly Roy 12 Feb '11

12 Feb '11

I have a top-level config file logback.xml and another file logback-included.xml. If I set the scan=true in the logback.xml file, will the included file also be scanned for changes? Is scan=true applicable for <included> tag as well? I find that the scanning doesn't happen, when I change the included file. Should I do anything special? --- logback.xml --- <configuration scan="true"> <include file="logback-included.xml" /> </configuration> --- logback-included.xml --- <included scan="true"> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>mylog.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>mylog.log.%d{yyyy-MM-dd}</FileNamePattern> </rollingPolicy> <encoder> <pattern>%date %level [%thread] %logger{15} %msg%n</pattern> </encoder> </appender> <root> <level value="DEBUG" /> <appender-ref ref="FILE" /> </root> </included> _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:…

4 7

Logback and Facebook Scribe
by BenT 21 Jan '11

21 Jan '11

Hi, Out of curiosity, has anybody used Facebook's scribe interface as a logging destination for logback? Thanks in advance, Ben -- View this message in context: http://old.nabble.com/Logback-and-Facebook-Scribe-tp28539373p28539373.html Sent from the Logback User mailing list archive at Nabble.com.

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

bug - Log4j XMLLayout does not encode data
by David Balažic 31 Aug '10

31 Aug '10

Hi! It seems the Log4j XMLLayout * does not properly XML encode data it puts into the output XML. Example: 116 buf.append("\" thread=\""); 117 buf.append(event.getThreadName()); 118 buf.append("\">\r\n"); The thread name can be any string, so it can include characters like <>"/'& etc... That would break the XML. * http://logback.qos.ch/xref/ch/qos/logback/classic/log4j/XMLLayout.html same in the logback 0.9.24 David Balažic Software Engineer ComTrade HERMES SoftLab a ComTrade company HERMES SoftLab d.o.o. Litijska 51, 1000 Ljubljana Slovenia phone: +386 81 60 8937 fax: +386 1 586 52 70 david.balazic(a)comtrade.com www.comtrade.com/si

1 0

DBAppender - turn off caller data logging. How?
by David Balažic 31 Aug '10

31 Aug '10

Hi! http://logback.qos.ch/manual/appenders.html The properties of DBAppender are not described. What exists besides connectionSource? Is there a way to turn off logging line numbers and other caller data? (performance!) Regards, David Balažic

1 0

Multiple JVMs writing to a single log file
by Becker, Thomas 27 Aug '10

27 Aug '10

I had a question about multiple JVMs writing to a single logfile. I'm aware of the "prudent" setting on FileAppender and that its purpose is to allow this. But we have noticed that we are getting the expected behavior without turning prudent mode on. That is, we are seeing the output of both processes interleaved in the single file even with prudent=false. So my question is, are we just getting lucky? Is this due to the platform we're running on (Linux) and will it break on Windows? Honestly we are probably going to switch to logging to separate files per application instance, I was just curious as to why this is working and what would be different ifwe enabled prudent mode.

2 2