February 2011 - logback-user

Re: [logback-user] Limiting events to one thread in email
by Benoit Xhenseval 01 Mar '11

01 Mar '11

Thanks Ceki, I had a look at this and I'm not too sure if it is the best approach or actually feasible... Allow me to give a few more details. 1) We're using the AsyncAppender as per http://jira.qos.ch/browse/LBCORE-92 (by the way, it would be great to include this in an official release!) 2) The processing can happen from a JMS Message or an RMI call, or a GUI event... there is no real single entry point where I would be able to put a value in MDC... Would a Cyclic Buffer per thread name in each event be a more appropriate approach? What do you think? I'm not sure we could use Thread.currentThread().getName() to distinguish each caller as the AsyncAppender would be using their own thread and not the one that actually originated the event... In which case, the interface get() on the CyclicBuffer is not suitable since I would have no way to give it the name of the thread that called the Error... Your opinion/suggestion/solution are appreciated, Thanks Benoit ----- Have a look at http://logback.qos.ch/recipes/emailPerTransaction.html HTH, -- Ceki On 17.02.2011 15:49, Benoit Xhenseval wrote: > Hi *, > > We're running an application on large multi-threaded servers. When an > exception/error occurs, we send an email with the last 50 DEBUG entries > or so. > > How could we ensure that these 50 entries are limited to the Thread that > is actually sending the error email? > > If there is no such implementation, what would be the recommended way? > > We can probably contribute it back to the community > > Many thanks > > Benoit > -- IMPORTANT NOTICE This communication contains information that is considered confidential and may also be privileged . It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and delete the original.

2 3

log4j StringMatchFilter porting to logback
by Fabio Erculiani 28 Feb '11

28 Feb '11

Hi there, it's me again, just wondering, what's the best way to reproduce the behaviour of log4j StringMatchFilter in logback? Do I have to use ch.qos.logback.core.filter.EvaluatorFilter ? Regards, -- Fabio Erculiani

3 9

Problem with configuring logback programatically
by Shahar.Kedar＠thomsonreuters.com 27 Feb '11

27 Feb '11

Hi, I'm using logback 0.9.28 and I'm trying to configure logback programmatically with the following code: public void prepare() { LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); lc.reset(); lc.getLogger("com").setLevel(Level.DEBUG); lc.getLogger("com.example").setLevel(Level.DEBUG); lc.getLogger("com.example.test").setLevel(Level.DEBUG); lc.getLogger("com.example.test.inner").setLevel(Level.DEBUG); PatternLayout patternLayout = new PatternLayout(); patternLayout.setContext(lc); patternLayout.setPattern("%-5level %logger - %msg%n"); patternLayout.start(); ConsoleAppender<ILoggingEvent> appender = new ConsoleAppender<ILoggingEvent>(); appender.setLayout(patternLayout); appender.setContext(lc); appender.start(); lc.getLogger("root").addAppender(appender); lc.start(); StatusPrinter.printInCaseOfErrorsOrWarnings(lc); super.prepare(testCase); } I keep getting the following message: LOGBACK: No context given for ch.qos.logback.core.ConsoleAppender[null]. I'm seeing the log messages in the console, but I fail to understand why I'm getting this message. Thanks, Shahar This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.

2 1

Re: [logback-user] MDC and env-entry
by José Juan Montiel 24 Feb '11

24 Feb '11

Hi, > Hi, again with another question. > > With aspectj, in injecting a var in MCD, something like this... > > MDC.put("code",var); > > in some places, depending something, and i'm using this to generate a > diferent file for this something like > > <appender name="APPENDER" > class="ch.qos.logback.classic.sift.SiftingAppender"> > <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> > <evaluator > class="ch.qos.logback.classic.boolex.JaninoEventEvaluator"> > <expression> > (marker != null) > && ( > (marker.contains("ASPECTJ")) || > (marker.contains("SOAP"))) > </expression> > </evaluator> > <onMatch>DENY</onMatch> > </filter> > <discriminator> > <Key>code</Key> > <DefaultValue>0000</DefaultValue> > </discriminator> > <sift> > <appender name="FILE-${code}" > class="ch.qos.logback.core.rolling.RollingFileAppender"> > <prudent>${prudent}</prudent> > >  > <encoder > class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> > <Pattern>%date - [%thread] - %.-20M - %L - > cn=%contextName - [%thread] - [%X{code}] - %message%n > %exception{5}</Pattern> > </encoder> > > <rollingPolicy > class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> > > > <FileNamePattern>${USER_HOME}/${backupDir}${code}.%d${patronRolling}</FileNamePattern> > > <MaxHistory>${maxHistory}</MaxHistory> > </rollingPolicy> > </appender> > </sift> > </appender> > > > ASPECTJ and SOAP are Markers of other traces, that i don't want to see > here. > This way i get > > in my root log directory ${USER_HOME}/${backupDir} files like > > 0001.log > 0002.log > > But, now i have multile apps (wars and ejbs) where i use > > web.xml > > <?xml version="1.0" encoding="UTF-8"?> > <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns=" > http://java.sun.com/xml/ns/javaee" xmlns:web=" > http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation=" > http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" > version="2.5"> > ... > > <env-entry> > <description>JNDI logging context for this app</description> > <env-entry-name>logback/context-name</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value>APP1</env-entry-value> > </env-entry> > <env-entry> > <description>URL for configuring logback context</description> > <env-entry-name>logback/configuration-resource</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value>logback.xml</env-entry-value> > </env-entry> > > ... > > </web-app> > > > > ejb-jar.xml > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise > JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> > <ejb-jar> > <enterprise-beans> > <session> > ... > > <env-entry> > <description>JNDI logging context for this app</description> > <env-entry-name>logback/context-name</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value>EJB1</env-entry-value> > </env-entry> > <env-entry> > <description>URL for configuring logback > context</description> > > <env-entry-name>logback/configuration-resource</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value>logback.xml</env-entry-value> > </env-entry> > > ... > </session> > </enterprise-beans> > > ... > </ejb-jar> > > a env-entry to identificate. I know that insede file, i use cn=%contextName > to see this context but... > > How could i use this context like i use ${code} to separete this files > (0001.log, 0002.log) in diferents directories. > > I'll make more simple... how to mix <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator"> <defaultValue>unknown</defaultValue> </discriminator> and <discriminator> <Key>code</Key> <DefaultValue>0000</DefaultValue> </discriminator> this is a MDC, form use %code (inside log line) like ${contextName} in name file. Can i have 2 discriminator inside 1 appender? PD: logback version 0.9.21. Thanks. -- Jose Juan Montiel Martinez Eurobits Technologies Calle Musgo 3, 1ª Planta 28023 Madrid T +34-917080300 F +34-913077480 josejuan.montiel(a)eurobits.es http://www.eurobits.com

2 1

Filter Throwable from Appender
by Markus Krainz 23 Feb '11

23 Feb '11

Hi, I am using two Appenders |ConsoleAppender and my own custom Gui||Appender which extends OutputStreamAppender. This works well. I do not want the GuiAppender to append Stacktraces. So if I do e.g. logger.error("Core: ERROR importing map.\n",ex); the "Throwable ex"-Stacktrace should get to ||ConsoleAppender||but not to ||Gui||Appender. I am relatively new to Logback and I appreciate any help with this. Regards, Markus |

2 2

decorating an Appender with additional behavior ?
by Andreas Andreakis 22 Feb '11

22 Feb '11

Hello, which is the preferred way to decorate an Appender with additional behavior ? Optimally, the new behavior should be applicable to any Appender. As an example consider the Cyclic Queue behavior of the SMPTAppender. A CyclicQueueAppender could implement this feature and delegate calls to a referenced concrete Appender, such that the feature can be utilized in other (non-SMTP) scenarios as well. Also (if currently possible) the Decorator should be configured declaratively within a configuration file. kind regards, Andreas

2 3

Logging to NT Event Log
by Shahar.Kedar＠thomsonreuters.com 18 Feb '11

18 Feb '11

Hi, Is there an appender which writes log event to the NT event log? Thanks, Shahar Kedar Software Engineer ClearForest, a Thomson Reuters company Thomson Reuters Phone: +972-73-2676014 shahar.kedar(a)thomsonreuters.com thomsonreuters.com This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.

3 5

GEventEvaluator never started.
by Aleksey Didik 18 Feb '11

18 Feb '11

Hello. Looks like I have found a little issue in work of GEventEvaluator. I have defined filter and expression in my logback.xml, but evaluator is not used during filtering process. I have debugged it and found, that GEventEvaluator is not started (started = false) but start() method called. I checked start() method and found it never calls super.start() neither set started manually. It's looks like an issue. Best regards, Aleksey. -- *Aleksey Didik,* System Architect Tel (Office): + 7 846 342 51 74 ext.242 Mob: +7 927 730 76 43 Skype ID: aleksey.didik *Maxifier - AOP Technology Award Winner 2010* *Confidential and/or legally privileged information may be in this email, which only the intended addressee(s) may access. If you have received this email in error, please inform us immediately and delete all copies from your system. Maxifier Limited uses anti-virus systems but can take no responsibility for any viruses which attach to this email.*

2 2

Limiting events to one thread in email
by Benoit Xhenseval 17 Feb '11

17 Feb '11

Hi *, We're running an application on large multi-threaded servers. When an exception/error occurs, we send an email with the last 50 DEBUG entries or so. How could we ensure that these 50 entries are limited to the Thread that is actually sending the error email? If there is no such implementation, what would be the recommended way? We can probably contribute it back to the community Many thanks Benoit ----- Important Notice This communication contains information that is considered confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and delete the original

2 1

How to avoid 'duplicate' emails
by Benoit Xhenseval 17 Feb '11

17 Feb '11

Hi * We are using smtpappender. Is there an official way to stop logback from mailing similar emails over and over? We think that this could be based on filtering out identical subjects and time window. Is there a solution out there? If not, what would be the recommended way to tackle this? Thanks Benoit ----- Important Notice This communication contains information that is considered confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and delete the original

2 1