August 2009 - logback-user - mailman3.qos.ch

DBAppender and timestmp as big int
by Mel T 14 Aug '09

14 Aug '09

We need to write our own DBAppender. I want us to have it very similar to the logback DBAppender (i.e. use the same DB schema plus our own fields). I wonder why this appender defines the date columns as big int. Are these some of the reasons ? - native dates are hard to support accross multiple DBs - timezone and DST can really hurt us. - it is faster to write a big int than a date where a clendar would have to be passed into the ps.setTimestamp calls. or are there other reasons? Mel T. -- View this message in context: http://www.nabble.com/DBAppender-and-timestmp-as-big-int-tp24956664p2495666… Sent from the Logback User mailing list archive at Nabble.com.

2 1

custom fields
by Mel T. 11 Aug '09

11 Aug '09

Hi, We have an in-house logger that we want to get rid of. This logger has application specific functionality. - We store logs in a database table - We have specific columns that put some very-frequently used context information - For that purpose, our logger has methods like this: log(String message, String someContextID1, String someContextID2, ...); - This is added to the DB with specific columns for someContextID1, someContextID2, etc... - We have a log viewer that allows to select logs based on that context information. So we need an appender that will continue to fill up that same table. If we move to a logger like logback, I am unsure how to best handle our application need. This first comes to mind: - Create our own facade that adds the specific log methods (like above) - This facade assembles these arguments into a parsable message given to sfl4j/logback - An in-house DBAppender can parse the message to extract the arguments and store them in the right column. Or is there a more natural way to do that? I looked at markers, MDC, but is is not clear to me if any of them would be good for that. Maybe MDC could be used that way: - Create our own facade that adds the specific log methods (like above) - This facade assembles these arguments and places them in MDC - An in-house DBAppender can read the MDC and store values in the right column. Also, is'nt adding another facade on top of SLF4J/logback a little too much? Since we may add out own facade, should'nt we directly use logback? -- Mel T.

4 3

RollingFileAppender with Prudent Flag
by Thomas.Guenter1＠swisscom.com 11 Aug '09

11 Aug '09

Hi, we're using logback and the RollingFileAppender to write log files from several webservice to a /logs directory and automatically move "old" files into a /logs/archive directory based on a TimeBasedRollingPolicy. This works great with the following configuration: <appender name="SERVICE_CALL_SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="com.myproject.logback.ContextEnvironmentPartBasedDiscriminator"> <DefaultValue>unknown</DefaultValue> </discriminator> <sift> <appender name="FILE-AUDIT-${environmentName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${LOG_DIR}/service_call_${environmentName}.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <FileNamePattern>${LOG_DIR}/archive/service_call_${environmentName}_%d{yyyy-MM-dd}.log</FileNamePattern>  <MaxHistory>${MAX_HISTORY_DAYS}</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss.SSS} [%contextName] refId: %mdc{refId}, %msg%n</Pattern> </layout> </appender> </sift> </appender> But since some of the log files are shared between different applications, I discovered some strange effects (one of the applications stopped writing into one of the log-files) and read about the prudent flag. Now, I tried to switch on the prudent mode using the following configuration: <appender name="SERVICE_CALL_SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="com.myproject.logback.ContextEnvironmentPartBasedDiscriminator"> <DefaultValue>unknown</DefaultValue> </discriminator> <sift> <appender name="FILE-AUDIT-${environmentName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${LOG_DIR}/service_call_${environmentName}.log</File>  <Prudent>true</Prudent> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <FileNamePattern>${LOG_DIR}/archive/service_call_${environmentName}_%d{yyyy-MM-dd}.log</FileNamePattern>  <MaxHistory>${MAX_HISTORY_DAYS}</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss.SSS} [%contextName] refId: %mdc{refId}, %msg%n</Pattern> </layout> </appender> </sift> </appender> This way, the node /appender/sift/appender/File isn't used anymore and the logger directly writes into the archive file specified under /appender/sift/appender/rollingPolicy/FileNamePattern. Is there a way of using the prudent mode but still separating the log from the archive files? Thanks for your help! tom

2 4

SLF4J and logback presentation
by Ceki Gulcu 10 Aug '09

10 Aug '09

Hello all, For those who are not afraid of being bored out of their skull, you can listen to my Jazoon 2009 presentation on SLF4J and logback for about 45 minutes, http://beta.parleys.com/#state=state_player&id=357 Yawn... you've been warned, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

Verbose status messages, even though no errors or warnings
by Rob W 10 Aug '09

10 Aug '09

Logback starts up verbosely when I use it and I can't figure out why. The documentation says this is supposed to happen if there are errors when it starts up, but there are none. I'm not manually invoking StatusPrinter.print() either. Anyone have any ideas what I might be missing here? I'm using logback 0.9.16 with slf4j-1.5.8. The status messages being shown are: 12:07:06,005 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 12:07:06,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/analytics/dist/conf/logback.xml] 12:07:06,108 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender] 12:07:06,112 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 12:07:06,151 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [layout] on top of the object stack. 12:07:06,192 |-INFO in ch.qos.logback.core.FileAppender[FILE] - File property is set to [etl.log] 12:07:06,192 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [FILE] from the object stack 12:07:06,192 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 12:07:06,192 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[root] 12:07:06,195 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.

2 1

A small mistake of the logback manual
by Jerry Huang 10 Aug '09

10 Aug '09

Hi, everyone I'm a newbie of logback. I found a small mistake of the logback manual in Chapter 3: Logback configuration. A *logger* element takes exactly one mandatory name attribute, an optional > level attribute, and an optional *aditivity *attribute, which admits the > values *true* or *false*. > The *aditivity* *should be **additivity* *, right? I tested for it and the **aditivity doesn't work.* * *-- Sent from Hangzhou, 33, China Joan Crawford<http://www.brainyquote.com/quotes/authors/j/joan_crawford.html> - "I, Joan Crawford, I believe in the dollar. Everything I earn, I spend."

2 1

Release of logback version 0.9.17
by Ceki Gulcu 09 Aug '09

09 Aug '09

9th of August 2009 - Release of version 0.9.17 I am happy to announce the immediate availability of logback version 0.9.17. In addition to important bug fixes this release adds often requested new features. Please refer to the the news page for precise details. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/logback-announce Best regards, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

Tomcat 5.5 and LogbackValve
by Chu, William 07 Aug '09

07 Aug '09

Hi all, I tried searching through the archives for any suggestions or answers to my dilemma so I must resort to posting this question. I'm attempting to use the LogbackValve with Tomcat 5.5 and I'm not achieving the results that I expected. What I'd like to do is have Tomcat use LogbackValve instead of org.apache.catalina.valves.FastCommonAccessLogValve. I attempted to follow the instructions detailed on this page, http://logback.qos.ch/access.html#tomcat, but to no avail. No log file is created in the TOMCAT_HOME/logs directory which I would expect it to do upon startup of Tomcat. What am I missing? Line in server.xml: <Valve className="ch.qos.logback.access.tomcat.LogbackValve"/> Logback-access.xml: <configuration debug="true"> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>access.log"</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>access.%d{yyyy-MM-dd}.log.zip</FileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>5MB</MaxFileSize> </triggeringPolicy> <layout class="ch.qos.logback.access.PatternLayout"> <Pattern>combined</Pattern> </layout> </appender> <appender-ref ref="FILE" /> </configuration> Regards, William Chu Sr. Applications Developer First American CoreLogic, Inc. Direct: 714.250.5813 Email: wchu(a)facorelogic.com ****************************************************************************************** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ****************************************************************************************** FACLD

3 9

dynamically creating/destroying logging appenders
by Bridges, Ed (Citco) 07 Aug '09

07 Aug '09

Hello, Following up from a comment from Ceci on StackOverflow: http://stackoverflow.com/questions/1239227/dynamically-creating-destroying-… I'd like to get context around his point that it is not possible, since it appears not only possible but quite easy. Likely I'm just missing something and would like to get more background about how to approach this problem. I quote here my original question: I have a legacy PSVM application which I'd like to redirect its logging output to unique files per execution. So, if I invoke it at 10:00, then have it redirect it's output to {thread-id}-10:00.log; and another thread of execution may begin an execution at 10:01, and its output would go to {thread-id}-10:01.log. I understand that this is not elegant. My questions are: · is this possible? · does someone have an idea of how to approach? · is it possible to release/destroy an appender when it's no longer needed? A suggestion I received on this posting proposed simply extending FileAppender. Based on that I created a simple (naïve?) class named "DynamicRuntimeFileAppender" like so: public class DynamicRuntimeFileAppender extends FileAppender { private static Logger log = Logger.getLogger(DynamicRuntimeFileAppender.class); public DynamicRuntimeFileAppender() { } public DynamicRuntimeFileAppender( Layout layout, String filename, boolean append, boolean bufferedIO, int bufferSize) throws IOException { super(layout, filename, append, bufferedIO, bufferSize); } public DynamicRuntimeFileAppender( Layout layout, String filename, boolean append) throws IOException { super(layout, filename, append); } public DynamicRuntimeFileAppender( Layout layout, String filename) throws IOException { super(layout, filename); } public static Appender configuredInstance(String filename) throws IOException { if(null == filename || filename.length() < 1) { throw new IllegalArgumentException("filename cannot be empty."); } HTMLLayout layout = new HTMLLayout(); layout.setTitle(filename); boolean append = false; DynamicRuntimeFileAppender appender = new DynamicRuntimeFileAppender(layout, filename, append); appender.setName(filename); appender.setBufferedIO(false); appender.setEncoding("UTF-8"); appender.setImmediateFlush(true); appender.setThreshold(Level.ALL); return appender; } } When I run it using a test like this, it appears to work fine: private static final Logger log = Logger.getLogger(Log4JTest.class); @Test public void testAddAppender() throws Exception { Appender a = DynamicRuntimeFileAppender.configuredInstance( buildFilename("target/Log4JTest") ); log.addAppender(a); log.info(format("test message using appender [%s]", a.getName())); log.removeAppender(a); a.close(); } Thank you very much. Ed Disclaimer link. To see it, click the link below, or copy and paste it into your browser's address line. http://www.citco.com/emaildisclaimer.htm

2 3

Logback, 2 ears and 1 jboss
by José Juan Montiel 07 Aug '09

07 Aug '09

Hi, this is my first time... :) There is some limit in the numbers of appender that i define in a file included? I have a logback.xml with 2 include... <include resource="logback-X1.xml"/> <include resource="logback-X2.xml"/> and de same number of appender in each file APP1_X1, APP2_X1... and APP1_X2, APP2_X2... And when application start server output... APP1_X1 APP1_X_n-(x) .. APP2_X2_n-(x+1) APP2_X2_n In a standalond example (1 jar, 1 jvm), works ok.... In a few words, this is the problem... And another question, diferences between documentation about wars/tomcat and ears/jboss? Thanks in advice, and greate job. PD: Git seems great for branches and branches... and offline, but as the first response, i thin there is good: "eclipse team sincronize" :) -- 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

3 3