- logback-user - mailman3.qos.ch

erratic smtpAppender behavior
by Palmer, Eric 28 Jun '13

28 Jun '13

I'm trying to get 5 emails sent and am getting 1 random one sent. log = LoggerFactory.getLogger("applogger"); //TODO Get emails sending logErr = LoggerFactory.getLogger("Error"); log.info("test logger"); logErr.error("test error message1"); logErr.error("test error message2"); logErr.error("test error message3"); logErr.error("test error message4"); logErr.error("test error message5"); log.error("from applogger"); try { Thread.sleep(5000); } catch(InterruptedException ex) { Thread.currentThread().interrupt(); } System.exit(0); Sends one email out of the 5 error messages and the one sent is not predictable. Config file <configuration debug="true"> <timestamp key="bySecond" datePattern="yyyyMMdd'T'HHmmss"/> <appender name="ERROREMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTracker">  <bufferSize>1</bufferSize> </cyclicBufferTracker> <smtpHost>mysmtp.host.edu</smtpHost> <to>epalmer(a)richmond.edu<mailto:epalmer@richmond.edu></to> <from>epalmer(a)richmond.edu<mailto:epalmer@richmond.edu></from> <subject>Error in DirPeople2Xml: %logger{20} - %m</subject> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date %-30(%d{HH:mm:ss.SSS} [%M]) %-5level %-33(%C{32}) - %msg%n</pattern> </layout> </appender> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%-30(%d{HH:mm:ss.SSS} [%M]) %-5level %-33(%C{32}) - %msg%n</pattern> </encoder> </appender> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>/Volumes/HD2/IDEAProjects/DirPeople2Xml/local/logs/log-${bySecond}.log</file> <append>true</append>  <encoder> <pattern>%-30(%d{HH:mm:ss.SSS} [%M]) %-5level %-33(%C{32}) - %msg%n</pattern> </encoder> </appender> <logger name="Error" level="error"> <appender-ref ref="ERROREMAIL" /> </logger> <root level="info"> <appender-ref ref="FILE" /> <appender-ref ref="STDOUT" /> </root> </configuration> Stdout messages 07:42:08,457 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 07:42:08,457 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at [file:/Volumes/HD2/IDEAProjects/DirPeople2Xml/target/classes/logback-test.xml] 07:42:08,573 |-INFO in ch.qos.logback.core.joran.action.TimestampAction - Using current interpretation time, i.e. now, as time reference. 07:42:08,575 |-INFO in ch.qos.logback.core.joran.action.TimestampAction - Adding property to the context with key="bySecond" and value="20130621T074208" to the LOCAL scope 07:42:08,575 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.net.SMTPAppender] 07:42:08,592 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ERROREMAIL] 07:42:08,690 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 07:42:08,693 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 07:42:08,697 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 07:42:08,703 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender] 07:42:08,705 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 07:42:08,708 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 07:42:08,708 |-INFO in ch.qos.logback.core.FileAppender[FILE] - File property is set to [/Volumes/HD2/IDEAProjects/DirPeople2Xml/local/logs/log-20130621T074208.log] 07:42:08,711 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [Error] to ERROR 07:42:08,711 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ERROREMAIL] to Logger[Error] 07:42:08,712 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 07:42:08,712 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT] 07:42:08,712 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 07:42:08,712 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 07:42:08,713 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@5e0feb48 - Registering current configuration as safe fallback point 07:42:08.717 [main] INFO e.r.i.w.D.PeopleXmlMain - some log message 07:42:08.721 [startApp] INFO e.r.i.w.DirPeople2Xml.AppInfo - test logger 07:42:08,728 |-INFO in ch.qos.logback.classic.net.SMTPAppender[ERROREMAIL] - SMTPAppender [ERROREMAIL] is tracking [1] buffers 07:42:08.721 [startApp] ERROR e.r.i.w.DirPeople2Xml.AppInfo - test error message1 07:42:08.728 [startApp] ERROR e.r.i.w.DirPeople2Xml.AppInfo - test error message2 07:42:08.728 [startApp] ERROR e.r.i.w.DirPeople2Xml.AppInfo - test error message3 07:42:08.729 [startApp] ERROR e.r.i.w.DirPeople2Xml.AppInfo - test error message4 07:42:08.729 [startApp] ERROR e.r.i.w.DirPeople2Xml.AppInfo - test error message5 07:42:08.730 [startApp] ERROR e.r.i.w.DirPeople2Xml.AppInfo - from applogger 07:42:08,754 |-INFO in ch.qos.logback.classic.net.SMTPAppender[ERROREMAIL] - About to send out SMTP message "Error in DirPeople2Xml: Error - test error message2" to [epalmer(a)richmond.edu<mailto:epalmer@richmond.edu>] 07:42:08,754 |-INFO in ch.qos.logback.classic.net.SMTPAppender[ERROREMAIL] - About to send out SMTP message "Error in DirPeople2Xml: Error - test error message5" to [epalmer(a)richmond.edu<mailto:epalmer@richmond.edu>] 07:42:08,755 |-INFO in ch.qos.logback.classic.net.SMTPAppender[ERROREMAIL] - About to send out SMTP message "Error in DirPeople2Xml: Error - test error message4" to [epalmer(a)richmond.edu<mailto:epalmer@richmond.edu>] 07:42:08,755 |-INFO in ch.qos.logback.classic.net.SMTPAppender[ERROREMAIL] - About to send out SMTP message "Error in DirPeople2Xml: Error - test error message1" to [epalmer(a)richmond.edu<mailto:epalmer@richmond.edu>] 07:42:08,755 |-INFO in ch.qos.logback.classic.net.SMTPAppender[ERROREMAIL] - About to send out SMTP message "Error in DirPeople2Xml: Error - test error message3" to [epalmer(a)richmond.edu<mailto:epalmer@richmond.edu>] Thanks in advance for help -- Eric Palmer Web Services U of Richmond

1 1

logback.groovy configuration with OSGI
by Ewgenij Sokolovski 28 Jun '13

28 Jun '13

Hello. I'm using logback as logging utility of my bundle integrated in Knopflerfish OSGI framework. In order to enable Groovy support I installed and started groovy-all-2.1.5.jar in the framework. However, I keep getting the following exception when I start the framework [stderr] Failed to instantiate [ch.qos.logback.classic.LoggerContext] [stderr] Reported exception: [stderr] groovy.lang.MissingPropertyException: No such property: FileAppender for class: Script1 [stderr] at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.ja va:50) [stderr] at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPrope rtySite.java:49) So, what's wrong here? :) Thank you for any support in advance! BR Ewgenij

1 0

Debug the groovy configuration file
by Ewgenij Sokolovski 28 Jun '13

28 Jun '13

Hello, I created a groovy configuration file but the logging does not create an output with it. So, I think I made some error there. But how can I debug the file? I do not see any error output anywhere? BR Ewgenij Sokolovski

1 0

Simplest Java sample; Simplest logback.xml; what no logfile
by Kundan Bapat 27 Jun '13

27 Jun '13

Single barebones Java file using slf4j package - 2 imports; Default package. barebones logbackxml - directly under classpath - which is 'current directory'. The log statements in file seen on console, but no FileAppender (file) created. Messing with logback.xml syntax makes no difference - means it is simply not read by the program. I can use help. This is my first trial with logback; only used log4j a while back. no groovy or maven nothing. plain command line javac and java. Java: import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class NMSLogger { private final Logger nmsLogger = LoggerFactory.getLogger(NMSLogger.class); public void sayHello(String name) { nmsLogger.info("INFO: Hi, {}", name); nmsLogger.info("INFO:Welcome to the NBN NMS LogBack World. Hello World!\n"); nmsLogger.error("EROR:Welcome to the NBN NMS LogBack World. Hello World!\n"); } public static void main(String[] args) { NMSLogger theLogger = new NMSLogger(); theLogger.sayHello("srccodes.com"); } } ------------- logback.xml: <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logFile.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern> logFile.%d{yyyy-MM-dd}.log.zip </FileNamePatter> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %d{HH:mm:ss,SSS} [%thread] %-5level %logger{22} - %msg%n </Pattern> </layout> <root level="${root-level:-debug}"> <appender-ref ref="FILE"/> </root> </appender> </configuration> ----------- dir: logback.xml NMSLogger.class NMSLogger.java slf4j-api-1.7.5.jar* slf4j-jdk14-1.7.5.jar ========== Any help, pointers please? -- View this message in context: http://logback.10977.n7.nabble.com/Simplest-Java-sample-Simplest-logback-xm… Sent from the Users mailing list archive at Nabble.com.

3 9

Grouping of log messages
by Hamish Graham 26 Jun '13

26 Jun '13

Hi, We currently use Logback (+slf4j) for all the logging in our application. We have a number of servers and we plan to aggregate the log files and use something like logstash to view them all. Does anyone know of a way to group the logs for a given request for easier debugging of issues. App Engine does this and it is incredibly convenient as it is possible to quickly see the flow for each user's request. This screenshot (not mine) shows what I mean: http://gwt-log.googlecode.com/files/2009-04-15-gwt-log-RemoteLogger-App-Eng… I'm not sure if this needs to be done at the logging side or not. Thanks, Hamish -- The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. dotMobi (Afilias Technologies Limited) is a private company limited by shares, incorporated and registered in the Republic of Ireland with registered number 398040 and registered office at First Floor, Fitzwilton House, Wilton Place, Dublin 2.

2 1

commons-cli dependency over commons-logging after replacing with jcl-over-slf4j
by Govardhana 26 Jun '13

26 Jun '13

Hi, As part of the migration from log4j to logback, i have replaced commons-logging jar with jcl-voer-slf4j jar but commons-cli jar has dependency over commons-logging, due to that, got maven build error. In this case, do we need to replace commons-cli with some other cli jar which will not have commons-logging jar dependency. I would request your help. Thanks, Govardhana -- View this message in context: http://logback.10977.n7.nabble.com/commons-cli-dependency-over-commons-logg… Sent from the Users mailing list archive at Nabble.com.

2 1

SMTPAppender - Email not formatted properly when log message contains double linebreak
by Arend v. Reinersdorff 25 Jun '13

25 Jun '13

Hi, when I a log message with a double linebreak "A\n\nA" to SMTPAppender, the resulting Email is not formatted properly. The MIME parts are not parsed but are display as the message body. It looks like the double linebreak is written directly into the Subject-Header. With a single linebreak I get the same problem in Gmail. In Outlook the email is formatted properly, only the subject is cut at the linebreak. Could this be a bug in Logback? Regards, Arend Logging call: LoggerFactory.getLogger(Main.class).error("A\n\nA"); logback.xml: <configuration> <root> <appender class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>... smtpHost</smtpHost> <to>... email</to> <subject>%logger{10} - %message</subject> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%logger{10} - %message</pattern> </layout> </appender> </root> </configuration> Email subject: c.e.l.Main - A Visible email body: A MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_0_14393847.1372070958822" ------=_Part_0_14393847.1372070958822 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit c.e.l.Main - A A ------=_Part_0_14393847.1372070958822-- Email source: ... email headers To: ... Message-ID: ... Subject: c.e.l.Main - A A MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_0_14393847.1372070958822" ------=_Part_0_14393847.1372070958822 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit c.e.l.Main - A A ------=_Part_0_14393847.1372070958822--

4 4

Custom variables and AsyncAppender in logback.groovy
by Marvin B. Lillehaug 22 Jun '13

22 Jun '13

Hi, I'm trying to convert my xml configuration to groovy, and are having some problems. When using xml I defined a variable ${logdir} where the logs should end up. In the xml config I just added logdir as a property in the LoggerContext, and reconfigured the context. and it worked. However it seems that these properties are not made available to the config script. The only variable made available is ${hostname} (GafferConfigurator.run(..)). The way I am configuring with groovy is: ContextInitializer contextInitializer = new ContextInitializer(loggerContext); contextInitializer.configureByResource(configFile); Is there som other way I should do this, or do I have to do some magic to get my variable? I also use AsyncAppender. In xml these are defined by referencing an existing appender with appender-ref="nameofexistingappender", but it seems this does not work when using groovy. Using appender-ref("nameofexistingappender"), AsyncAppender.addAppender(..) is called, but the argument is null. Using http://jira.qos.ch/browse/LOGBACK-269 does work, but after all it is a hack. -- Marvin B. Lillehaug

1 1

JVM Crash (SIGSERV) on PackagingDataCalculator.getCodeLocation
by Andre Pereira 21 Jun '13

21 Jun '13

Hi, I'm getting a weird random JVM crashes with a web application deployed on tomcat6 using logback. As can be seen below, the crash apparently occurs on a code executed by logback. Attached is the hs_err_pid8814.log<http://logback.10977.n7.nabble.com/file/n12551/hs_err_pid8814.log> file generated. Any clues? # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf3712568, pid=8814, tid=8215360 # # JRE version: 6.0_43-b01 # Java VM: Java HotSpot(TM) Server VM (20.14-b01 mixed mode linux-x86 ) # Problematic frame: # j ch.qos.logback.classic.spi.PackagingDataCalculator.getCodeLocation(Ljava/lang/Class;)Ljava/lang/String;+20 # # An error report file with more information is saved as: # /java/apache-tomcat-6.0/server/petpg/hs_err_pid8814.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp #

2 2

Re: [logback-user] Logback-user Digest, Vol 21, Issue 21
by David Tkaczyk 21 Jun '13

21 Jun '13

For this problem: 1. Logs not displaying line numbers (praveen patil) you may need to compile with debug turned on... On Fri, Jun 21, 2013 at 7:09 AM, <logback-user-request(a)qos.ch> wrote: > Send Logback-user mailing list submissions to > logback-user(a)qos.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qos.ch/mailman/listinfo/logback-user > or, via email, send a message with subject or body 'help' to > logback-user-request(a)qos.ch > > You can reach the person managing the list at > logback-user-owner(a)qos.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Logback-user digest..." > > Today's Topics: > > 1. JVM Crash (SIGSERV) on > PackagingDataCalculator.getCodeLocation (Andre Pereira) > > > ---------- Forwarded message ---------- > From: Andre Pereira <andreptb(a)gmail.com> > To: logback-user(a)qos.ch > Cc: > Date: Fri, 21 Jun 2013 08:08:39 -0300 > Subject: [logback-user] JVM Crash (SIGSERV) on > PackagingDataCalculator.getCodeLocation > > Hi, > > I'm getting a weird random JVM crashes with a web application deployed on > tomcat6 using logback. As can be seen below, the crash apparently occurs on > a code executed by logback. Attached is the hs_err_pid8814.log<http://logback.10977.n7.nabble.com/file/n12551/hs_err_pid8814.log> file > generated. Any clues? > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0xf3712568, pid=8814, tid=8215360 > # > # JRE version: 6.0_43-b01 > # Java VM: Java HotSpot(TM) Server VM (20.14-b01 mixed mode linux-x86 ) > # Problematic frame: > # j > ch.qos.logback.classic.spi.PackagingDataCalculator.getCodeLocation(Ljava/lang/Class;)Ljava/lang/String;+20 > # > # An error report file with more information is saved as: > # /java/apache-tomcat-6.0/server/petpg/hs_err_pid8814.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > > _______________________________________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user >

1 0