- logback-user - mailman3.qos.ch

Log4j LoggingEvent
by Greg Flex 14 May '09

14 May '09

Hi Ceki, I (again) have some questions about log4j. (I guess Logback works the same way....) I was wondering if there's a way to save a "logger object" to a data structure like a queue or something before sending it to some appender. For example: The socket appender will cause the log4j client to lock/freeze if there's no link to the server. I verified it and it does lock the client. I need to deal with this issue so I'd like to store "logger objects" (or something) before they go to the socket or some other appender first. At the moment I have a wrapper around the log4j that when the debug method is called I'm just calling the log4j debug method passing some args etc. so I have: logger.debug("some stuff"); The configuration file does the trick and outputs to the console (at the moment) all the info: the class name, the method name, the line number etc. I'd like to save this info somehow to some object that I can store in a queue or something. How do I retrieve this information programmatically? Is there a way? I know about LoggingEvent object, could I use it and pass the above stated information to its constructor then store it in a queue? Logger gets me for free (like method name etc.) Any suggestion? Thanks a lot. Greg.

3 7

breaking on startup
by Brian Moschel 13 May '09

13 May '09

Hey guys, I am noticing an error on startup: java.lang.ClassCastException: org.slf4j.impl.SimpleLoggerFactory I am trying to run the following lines to load my config, which I got from the startup guide: LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator configurator = new JoranConfigurator(); lc.reset(); configurator.setContext(lc); configurator.doConfigure(my_path); StatusPrinter.printInCaseOfErrorsOrWarnings(lc); The error occurs at the first line in the above code. I got this working at some point, but somehow am back in a non-working state. This is a Jetty app. Any tips? Thanks, Brian

3 8

Exception Handler
by Brian Moschel 12 May '09

12 May '09

Hey guys, I have a Jetty application that I configured with Logback. I am trying to set it up so any errors that occur during execution are emailed to me. I am a bit of a noobie, and so far I haven't had any luck with this. I can only get exceptions emailed to me if I explicitly set a try/catch block in my code everywhere and call logger.error(...). Is there an easy way to cause all exceptions to be logged and emailed to me via my SMTPAppender? Here is the config I have attempted to use so far: <configuration debug="true"> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>smtp.gmail.com</SMTPHost> <SMTPPort>465</SMTPPort> <SSL>true</SSL> <Username>myemail</Username> <Password>my password</Password> <To> myemail</To> <From> myemail</From> <Subject>TESTING: %logger{20} - %m</Subject> <layout class="ch.qos.logback.classic.html.HTMLLayout"/> </appender> <root level="debug"> <appender-ref ref="EMAIL" /> </root> <logger name="exception" level="ERROR"> <appender-ref ref="EMAIL"></appender-ref> </logger> <logger name="org.mortbay" level="error"> <appender-ref name="EMAIL"> </appender-ref></logger> <logger name="developerworks.jetty6" level="error"> <appender-ref name="EMAIL"> </appender-ref></logger> <logger name="jupiter.filters" level="error"> <appender-ref name="EMAIL"> </appender-ref></logger> <logger name="jupiter.messaging" level="error"> <appender-ref name="EMAIL"> </appender-ref></logger> </configuration> Thanks, Brian

3 2

Lilith 0.9.35 has been released!
by Joern Huxhorn 02 May '09

02 May '09

This release brings a big performance increase in both the Lilith application itself and the Lilith appenders Additionally, Lilith now supports the import of LOG4J and java.util.logging XML files Please see changes for more details on whats new. http://sourceforge.net/project/shownotes.php?group_id=219536&release_id=679… http://lilith.huxhorn.de At this point, the Lilith artifacts hav reached the central maven repository. Regards, Joern.

1 0

Re: [logback-user] Setting up trace only for a certain user
by Christophe Elek 28 Apr '09

28 Apr '09

Salut Ceki, Thanks for the info... but... :) one question tough, what about the dynamicity (sic? :) the code I see suggests the developer enters the variable at runtime into a List/Map if I want to be as 'detached as possible' from the code, is there a way log4j can setup variables or am I 'stuck' with system variable ? Christophe Elek - Senior Software Analyst IBM Rational Serviceability Architect IBM Toronto Lab 8200 Warden Avenue, Markham, Ontario, L6G 1C7 Phone Number: (905) 413-3467 Email: celek(a)ca.ibm.com Rational Internal Serviceability Portal "Don't just fix the mistakes - fix whatever permitted the mistake in the first place." Charles Fishman Web:http://www.ibm.com/software/rational/ From: Ceki Gulcu <ceki(a)qos.ch> To: Log4J Users List <log4j-user(a)logging.apache.org> Date: 04/27/2009 09:19 AM Subject: Re: Setting up trace ony for a certain user Hello Christophe, SiftingAppender is prefect for this type of separation. See http://logback.qos.ch/manual/appenders.html#SiftingAppender for more information. If you intend to pursue this venue, please respond on the logback-user mailing list. Do not respond here. Christophe Elek wrote: > Hello, > I want to setup a trace only for a certain user. > How could I 'kill two birds with one stone ' and do something like > > log4j.logger.com.company.authorization.trace=joe(a)company.com > > so this enables the trace and I now what user to trace for ... :) > > thoughts ? > > Christophe Elek - Senior Software Analyst > IBM Rational Serviceability Architect -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe(a)logging.apache.org For additional commands, e-mail: log4j-user-help(a)logging.apache.org

3 2

Flushing Buffer
by Greg Flex 21 Apr '09

21 Apr '09

Hi Guys, Please ignore my last message. I figure this out..... Never mind........ Simple typo screwed things up..... Thanks. Greg.

1 0

Flushing Buffer
by Greg Flex 21 Apr '09

21 Apr '09

Hi Ceki, I'm getting no replies from Log4J guys so I thought I ask you.... I'm trying to change the appender (read from the config file) from Console to File at runtime. and I'm doing it by calling the DOMConfigurator.configure(String file) I'm getting some unexpected results however that I'm not sure how to fix. The Console appender does its job and the log messages are printed to the console as expected. (let say I'm printing only 5 log messages) Then I re-read the config file (by calling the above stated DOMConfigurator.configure(newConfigFile) method) that has a File appender in it. (another set of 5 log messages should be written to the file.) What I see in the file are 10 messages not 5.... The ones that I printed earlier to the console plus 5 new ones - after I changed the appender. I'm guessing that there is some kind of buffer that temporarily stores these log messages. Is there? How can I clear it so that when I re-read my config file with different appender, previous log messages (if any) won't be wrriten there? Any suggestion? Thanks Greg.

1 0

Logback eclipse plugin %message is null / SocketAppender
by tjodes＠vitaphone.de 21 Apr '09

21 Apr '09

Hello logback-users, I've encountered an issue concerning the logback eclipse plugin. It does not work correctly with the current logback bundles version 0.9.15; Are there any efforts in getting that logback plugin work against the current release? The were some minor changes that causes SocketAppender not showing messages in the "logback view"; %message returns/is null. sincerly yours, Thomas Hinweis: Diese Email enthält evtl. vertrauliche und rechtlich geschützte Informationen. Sollten Sie nicht der richtige Adressat sein oder diese Email irrtümlich erhalten haben, informieren Sie bitte sofort den Absender, und löschen Sie anschließend diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe des Inhalts dieser Email sind nicht gestattet. Attention: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this e-mail in error, please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents of this e-mail is strictly prohibited.

1 0

Re: [logback-user] TimeBasedRollingPolicy
by paha 19 Apr '09

19 Apr '09

Hi, sorry for popping up an old thread but i don't catch something: shouldn't the Logger when new event arrives check the last modification time of the log file and if it "is time" roll it over? i have the same configuration in servlet and script - rollover at midnight. in servlet everything works just fine. but in script, that is run from cron every 2 hours, events are always written in the same log. How can i make something, that doesn't run continually trigger rollover? -- View this message in context: http://www.nabble.com/TimeBasedRollingPolicy-tp19756004p22517998.html Sent from the Logback User mailing list archive at Nabble.com.

2 14

Log File Last Modified Not Changing
by Scott Malinowski 14 Apr '09

14 Apr '09

I found a wierd error that may be a bug (or I could be doing something stupid). I can see that records are being added to my log file but the last modified date/time is not changing. The timestamp is set to when the server came up and that is it. It never changes again. I can see this in Windows Explorer but this is also true via Java when using File.lastModified(), the value returned is always the same. Has anyone else seen this? I'm setting ImmediateFlush to true and when I look at the log file in TextPad, I am prompted to refresh everytime a new message is logged so I know the log file is being updated. I'm using Windows XP, WebLogic 9.1, and JDK 1.5. Thanks, Scott Here is my config file: <?xml version="1.0" encoding="UTF-8"?> <configuration>   <appender name="ERRORLOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <Append>true</Append> <ImmediateFlush>true</ImmediateFlush> <File>/var/log/iperms/uci/error.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-31(%-23date{MM-dd-yyyy HH:mm:ss.SSS} [%-5level]) %-17mdc{Process} \(%class.%method:%line\) %msg%n</Pattern> </layout> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>WARN</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <MaxHistory>30</MaxHistory> <FileNamePattern>/var/log/iperms/uci/error.%d.log</FileNamePattern> </rollingPolicy> </appender>  <appender name="INFOLOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <ImmediateFlush>true</ImmediateFlush> <Append>true</Append> <File>/var/log/iperms/uci/info.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-31(%-23date{MM-dd-yyyy HH:mm:ss.SSS} [%-5level]) %-17mdc{Process} \(%class.%method:%line\) %msg%n</Pattern> </layout> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <MaxHistory>30</MaxHistory> <FileNamePattern>/var/log/iperms/uci/info.%d.log</FileNamePattern> </rollingPolicy> </appender>  <appender name="VERBOSELOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>/var/log/iperms/uci/verbose.log</File> <ImmediateFlush>true</ImmediateFlush> <Append>true</Append> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-31(%-23date{MM-dd-yyyy HH:mm:ss.SSS} [%-5level]) %-17mdc{Process} \(%class.%method:%line\) %msg%n</Pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <MaxHistory>30</MaxHistory> <FileNamePattern>/var/log/iperms/uci/verbose.%d.log</FileNamePattern> </rollingPolicy> </appender>  <appender name="IMAGE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <ImmediateFlush>true</ImmediateFlush> <File>/var/log/iperms/uci/image.log</File> <Append>true</Append> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-31(%-23date{MM-dd-yyyy HH:mm:ss.SSS} [%-5level]) %-17mdc{Process} \(%class.%method:%line\) %msg%n</Pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <MaxHistory>30</MaxHistory> <FileNamePattern>/var/log/iperms/uci/image.%d.log</FileNamePattern> </rollingPolicy> </appender>  <appender name="SQL" class="ch.qos.logback.core.rolling.RollingFileAppender"> <Append>true</Append> <File>/var/log/iperms/uci/sql.log</File> <ImmediateFlush>true</ImmediateFlush> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-31(%-23date{MM-dd-yyyy HH:mm:ss.SSS} [%-5level]) %-17mdc{Process} \(%class.%method:%line\) %msg%n</Pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <MaxHistory>30</MaxHistory> <FileNamePattern>/var/log/iperms/uci/sql.%d.log</FileNamePattern> </rollingPolicy> </appender>  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger{36} - %msg%n</Pattern> </layout> </appender>  <logger name="DEFAULT" additivity="false" level="DEBUG"> <appender-ref ref="ERRORLOG" /> <appender-ref ref="INFOLOG" /> <appender-ref ref="VERBOSELOG" /> </logger> <logger name="IMAGE" additivity="false" level="INFO"> <appender-ref ref="IMAGE" /> </logger> <logger name="SQL" additivity="false" level="INFO"> <appender-ref ref="SQL" /> </logger>  <logger name="org.hibernate.connection.UserSuppliedConnectionProvider" level="ERROR" /> <logger name="org" level="WARN" /> <logger name="org.apache.commons.httpclient" level="ERROR" /> <logger name="httpclient" level="ERROR" /> <root level="debug"> <appender-ref ref="STDOUT" /> </root> </configuration>

1 0