April 2008 - logback-user - mailman3.qos.ch

MDC performance concerns
by Matthew Finn 01 May '08

01 May '08

Hello, I am interested in converting my application to logback, but I have some performance concerns about its MDC implementation. My application uses MDC extensively for async IO, so it may call MDC.put and MDC.remove extremely frequently, because each thread may be handling 1000s of interleaved connections using state machines. I see in the source for LogbackMDCAdapter that for every call to MDC.put and MDC.remove, the HashMap is cloned. Could this clone potentially be handled during the creation of LoggingEvents instead of the call to MDC? The creation of logging events is expected to entail memory allocation, so it seems that it would be a better fit there, even if some applications might have a very low number of calls to MDC versus logging calls. It seems that the same energy expended in minimizing log statement impact when logging is turned off should also apply to MDC calls. Thanks Matt

2 2

specify absolute path for logback.xml
by dvd＠newfoundmarket.com 28 Apr '08

28 Apr '08

Hello: I saw the thread discussing using system property to specify file path for logback.xml instead of solely use class path. I have the same issue too (surprised, actually). It is quite common to have config file separate from the war file so that support person(and developer) could adjust it for quick debugging. often it takes far more steps to rebuild/package the war file just to change the logging options. Perhaps a middle ground would be only have a single system property to specify the absolute path and leave the rest to application itself? Or allow a path parameter to be passed in getLogger() method and leave it to app to fingure out how to get the path?

1 0

Migrating to JIRA
by Ceki Gulcu 22 Apr '08

22 Apr '08

Hello All, I am thinking for migrating our bug reporting system to JIRA instead of bugzilla. The user interface looks a bit nicer and most importantly, I have the impression that email addresses are not visible to users not logged, which should make it harder for spammers to collect email addresses. You can see our *trial* installation at http://jira.qos.ch Please do not use it for filing reports just yet. -- Ceki Gülcü QOS.ch is looking to hire talented developers in Switzerland. If interested, please contact c e k i AT q o s . c h

2 1

duplicate messages with only a single logger in the logger context.
by Gibbons, P (Paul) 15 Apr '08

15 Apr '08

Hi my setup consists of: serverProcess - generates messages which are sent via SocketAppender to guiProcess and viewerProcess guiProcess - displays messages received from serverProcess and also generates messages which it displays and are sent via SocketAppender to viewerProcess viewerProcess - displays messages received from guiProcess and serverProcess. My problem is that messages generateg by serverProcess appear twice on viewerProcess. One instance comes directly from serverProcess and the other from guiProcess. The guiProcess is treated messages from serverProcess as local messages and so sends them via its SocketAppender to the viewerProcess. I cannot use filters to prevent the guiProcess SocketAppender resending the serverProcesses as the message formats are the same from both the serverProcess and guiProcess. One option could be to use a different logger context in the guiProcess handling of messages it receives from serverProcess. I am not sure of how to create a logger context which is not the default logger context for the application. Can anyone suggest how best to prevent the guiProcess from resending the messages it receives from the serverProcess or any other way of preventing the duplication of messages appearing on the viewerProcess. I suppose I could somehow simply drop a message from being processed on the viewerProcess if it is the same as the previous message; I am not sure how to do this however. Thanks Paul <DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom </FONT></DIV>

2 6

Re: [logback-user] GPL+Classpath exception
by Arthur Blake 12 Apr '08

12 Apr '08

Ceki: I hope I didn't offend with these questions about your licensing (the lack of any answer leaves me wondering...) The example "logblaster" might be a worst case scenario of someone ripping off an open source project for commercial gain. I certainly am not intending to make such a project -- more just probing as to what the intent of your license is and how far it could be stretched. I'm also really curious to know why you chose to switch from apache (log4j) to LGPL (logback) -- for my own knowledge. I have several open source projects, and it's always a headache trying to pick the right license whenever I start a new project. I learned a lot about the ends and outs from reading a few books on open source projects (especially "Producing Open Source Software" by Karl Fogel), but it's still always seems like a chore and a hassle to pick the right license. Any insight into your thought process on picking the license would be appreciated. If these questions are not appropriate for the list I apologize and you can feel free to send me a private email. ----- Original Message ---- From: Arthur Blake <blakesys(a)yahoo.com> To: logback users list <logback-user(a)qos.ch> Sent: Tuesday, April 8, 2008 3:04:01 PM Subject: Re: [logback-user] GPL+Classpath exception I guess what is more important to me is what you as the owner and author, are intending to allow and disallow with the license... For example, I think it's clear that you want to allow anyone to use logback as a logging system in any kind of software... proprietary, open source and otherwise. But what if someone created a completely new logging system and called it say "logblaster" that used logback as its core engine, but exposed some other API on top of it (this could be done completely without modifying logback-- just by including logback on the classpath) and packaged logblaster for sale as a proprietary product. Is that permissible? A normal GPL license would not allow that... it would require logblaster to be GPL too. An Apache style license would allow it. I think that technically even the GPL+classpath would allow that... but is that something you would be against? Do you want to allow extensions like that or not? BTW: interesting article here: http://en.wikipedia.org/wiki/GPL_linking_exception ----- Original Message ---- From: Ceki Gulcu <listid(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Sent: Tuesday, April 8, 2008 2:09:16 PM Subject: Re: [logback-user] GPL+Classpath exception IANAL, but it seems to me that both LGPL and GPL+classpath do not allow for direct extensions to be distributed under another license. However, combined and independent work (as in work merely using logback) is not affected by the provisions of the LGPL or GPL+classpath. As I understand it, the objections against the LGPL are due to the fuzzy nature of the extend to which the LGPL applies. I hate to admit that even with the classpath exception the meaning of "independent" is not 100% clear. IMHO, the LGPL does not fair any better. Arthur Blake wrote: > I absolutely agree that LGPL or GPL+classpath are valid and reasonable > licenses... it just makes it a little less business friendly. > > Does the GPL+classpath allow for writing extensions and plugins for > logback that I can license as a non-copyleft license (apache /BSD/X11 or > closed source)? > -- Ceki Gülcü QOS.ch is looking to hire talented developers in Switzerland. If interested, please contact c e k i @ q o s . c h _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

No context given for compiler/Parser Error with SimpleMDC example
by Daniel King 11 Apr '08

11 Apr '08

Any help would be greatly appreciated since I want my company to change over from log4j to slf4j and logback. However with this error, I won't be able to change over to logback only slf4j. I searched the archives and found no bug or solution for this error: LOGBACK: No context given for ch.qos.logback.core.pattern.parser.Compiler@4a65e0 15:10:23.205 [main] INFO chapter7.SimpleMDC - Check enclosed. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n15:10:23.220 [main] DEBUG chapter7.SimpleMDC - The most beautiful two words in English. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n15:10:23.220 [main] INFO chapter7.SimpleMDC - I am not a crook. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n15:10:23.220 [main] INFO chapter7.SimpleMDC - Attributed to the former US president. 17 Nov 1973. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n I'm using the following: Windows XP JDK 1.6 I created a directory named logback. I put the following jars in it: logback-core-0.9.9.jar logback-classic-0.9.9.jar logback-examples-0.9.9.jar slf4j-api-1.5.0.jar (I also tried slf4j-api-1.4.3.jar with same results) I created a bat file named SimpleMDC.bat. It contains the following: java -classpath "slf4j-api-1.5.0.jar;logback-core-0.9.9.jar;logback-classic-0.9.9.jar;lo gback-examples-0.9.9.jar;" chapter7.SimpleMDC I opened a command prompt and ran the bat file with the following output: C:\logback>SimpleMDC C:\logback>java -classpath "slf4j-api-1.5.0.jar;logback-core-0.9.9.jar;logback-classic-0.9.9.jar;lo gback-examples-0.9.9.jar;" chapter7.SimpleMDC LOGBACK: No context given for ch.qos.logback.core.pattern.parser.Compiler@4a65e0 15:10:23.205 [main] INFO chapter7.SimpleMDC - Check enclosed. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n15:10:23.220 [main] DEBUG chapter7.SimpleMDC - The most beautiful two words in English. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n15:10:23.220 [main] INFO chapter7.SimpleMDC - I am not a crook. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n15:10:23.220 [main] INFO chapter7.SimpleMDC - Attributed to the former US president. 17 Nov 1973. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n It might be of interest that whenever I used 0.8.1, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6 and 0.9.7 core and classic jars I got the following error when running the SimpleMDC code in a Maven 2 project using Eclipse 3.3 I created: SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder". SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details. Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/impl/StaticMDCBinder at org.slf4j.MDC.<clinit>(MDC.java:69) at com.vurv.logging.MDCLogging.main(MDCLogging.java:15) However, whenever I used 0.9.8 and 0.9.9 core and classic jars I got the same parser_error as listed above. Also the Ch# 7 example in the docs is missing this line of code: import ch.qos.logback.classic.spi.LoggingEvent; It is in the SimpleMDC code in the examples jar though. I also took this same project and copied it. Then I changed it over to use slf and log4j. I changed the logback code to log4j like this: Replace this code: // Configure logback PatternLayout layout = new PatternLayout(); layout.setPattern("%X{first} %X{last} - %m%n"); layout.start(); ConsoleAppender<LoggingEvent> appender = new ConsoleAppender<LoggingEvent>(); appender.setLayout(layout); appender.start(); // cast root logger to c.q.logback.classic.Logger so that we can attach an // appender to it ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) LoggerFactory.getLogger("root"); root.addAppender(appender); With this code: PatternLayout layout = new PatternLayout(); layout.setConversionPattern("%X{first} %X{last} - %m%n"); ConsoleAppender appender = new ConsoleAppender(layout); BasicConfigurator.configure(appender); The rest of the code is identical. This produced the correct output with slf4j and log4j. Dorothy Parker - Check enclosed. Dorothy Parker - The most beautiful two words in English. Richard Nixon - I am not a crook. Richard Nixon - Attributed to the former US president. 17 Nov 1973. Thanks, Daniel

2 2

Please unsubscribe
by Daniel Rossi 09 Apr '08

09 Apr '08

I thought i would never have to ask this. Ive tried about 10 times to request to unsubscribe but it wont. Thankyou.

1 0

Re: [logback-user] GPL+Classpath exception
by Arthur Blake 08 Apr '08

08 Apr '08

I guess what is more important to me is what you as the owner and author, are intending to allow and disallow with the license... For example, I think it's clear that you want to allow anyone to use logback as a logging system in any kind of software... proprietary, open source and otherwise. But what if someone created a completely new logging system and called it say "logblaster" that used logback as its core engine, but exposed some other API on top of it (this could be done completely without modifying logback-- just by including logback on the classpath) and packaged logblaster for sale as a proprietary product. Is that permissible? A normal GPL license would not allow that... it would require logblaster to be GPL too. An Apache style license would allow it. I think that technically even the GPL+classpath would allow that... but is that something you would be against? Do you want to allow extensions like that or not? BTW: interesting article here: http://en.wikipedia.org/wiki/GPL_linking_exception ----- Original Message ---- From: Ceki Gulcu <listid(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Sent: Tuesday, April 8, 2008 2:09:16 PM Subject: Re: [logback-user] GPL+Classpath exception IANAL, but it seems to me that both LGPL and GPL+classpath do not allow for direct extensions to be distributed under another license. However, combined and independent work (as in work merely using logback) is not affected by the provisions of the LGPL or GPL+classpath. As I understand it, the objections against the LGPL are due to the fuzzy nature of the extend to which the LGPL applies. I hate to admit that even with the classpath exception the meaning of "independent" is not 100% clear. IMHO, the LGPL does not fair any better. Arthur Blake wrote: > I absolutely agree that LGPL or GPL+classpath are valid and reasonable > licenses... it just makes it a little less business friendly. > > Does the GPL+classpath allow for writing extensions and plugins for > logback that I can license as a non-copyleft license (apache /BSD/X11 or > closed source)? > -- Ceki Gülcü QOS.ch is looking to hire talented developers in Switzerland. If interested, please contact c e k i @ q o s . c h _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

1 0

Re: [logback-user] GPL+Classpath exception
by Arthur Blake 08 Apr '08

08 Apr '08

I absolutely agree that LGPL or GPL+classpath are valid and reasonablelicenses... it just makes it a little less business friendly. Does the GPL+classpath allow for writing extensions and plugins for logback that I can license as a non-copyleft license (apache /BSD/X11 or closed source)? ----- Original Message ---- From: Ceki Gulcu <listid(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Sent: Tuesday, April 8, 2008 12:42:41 PM Subject: Re: [logback-user] GPL+Classpath exception Logback is related to log4j, but it is not an Apache project. The difference in license is one way to get the point across. Moreover, LGPL or GPL+classpath exception are both valid and reasonable licenses for libraries such as logback. Arthur Blake wrote: > I'm just curious... why did you decide not to use the Apache license for > logback... ? -- Ceki Gülcü QOS.ch is looking to hire talented developers in Switzerland. If interested, please contact c e k i @ q o s . c h _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

2 1

Re: [logback-user] GPL+Classpath exception
by Arthur Blake 08 Apr '08

08 Apr '08

I'm just curious... why did you decide not to use the Apache license for logback... ? ----- Original Message ---- From: Ceki Gulcu <listid(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Sent: Tuesday, April 8, 2008 5:34:31 AM Subject: [logback-user] GPL+Classpath exception Hello all, After recent discussions on the logback user list, I tentatively changed the license of logback to GPL with a "Classpath" exception. The terms of GPL+classpath exception are identical to the licensing terms of Java 7. Your comments are welcome, -- Ceki Gülcü QOS.ch is looking to hire talented developers in Switzerland. If interested, please contact c e k i @ q o s . c h _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

2 1