- logback-user - mailman3.qos.ch

Maven error installing logback
by Scott Miller 22 Dec '11

22 Dec '11

I am using the introduction in the documentation as my guide. I am new to Maven and logback. When I run mvn install I get one test error. It is testAppendAccessEvent(ch.qos.logback.access.db.DBAppenderTest) How can I fix this to complete Maven install? Scott

2 1

Re: [logback-user] logback - no applicable action - using the example from chapter 4
by Nadia Kunkov 21 Dec '11

21 Dec '11

Please, disregard my question... I was using the wrong type of the File Appender... Thank you Nadia ------------------------------------------------------------------------------------ Hello, Trying the logback file appender and all went well until I created the Rolling and Triggering policies. I'm following the examples in Chapter 4, so not sure how can this be wrong. The errors and the logback.xml are below: 16:13:23,158 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@25:78 - no applicable action for [rollingPolicy], current pattern is [[configuration][appender][rollingPolicy]] 16:13:23,158 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@26:24 - no applicable action for [fileNamePattern], current pattern is [[configuration][appender][rollingPolicy][fileNamePattern]] 16:13:23,159 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@27:17 - no applicable action for [minIndex], current pattern is [[configuration][appender][rollingPolicy][minIndex]] 16:13:23,159 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@28:17 - no applicable action for [maxIndex], current pattern is [[configuration][appender][rollingPolicy][maxIndex]] 16:13:23,159 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@31:85 - no applicable action for [triggeringPolicy], current pattern is [[configuration][appender][triggeringPolicy]] 16:13:23,160 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@32:20 - no applicable action for [maxFileSize], current pattern is [[configuration][appender][triggeringPolicy][maxFileSize]] <configuration> <contextName>Test</contextName> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>${JBOSS_HOME}/server/default/log/myApp.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>myApp.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>5</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1KB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%date %contextName %level [%thread] %logger{36} [%file:%line] %msg%n</pattern> </encoder> </appender> <logger name="com.test.logback" level="DEBUG" /> <root level="debug"> <appender-ref ref="FILE" /> <appender-ref ref="STDOUT" /> </root> </configuration> Nadia

1 0

logback - no applicable action - using the example from chapter 4
by Nadia Kunkov 21 Dec '11

21 Dec '11

Hello, Trying the logback file appender and all went well until I created the Rolling and Triggering policies. I'm following the examples in Chapter 4, so not sure how can this be wrong. The errors and the logback.xml are below: 16:13:23,158 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@25:78 - no applicable action for [rollingPolicy], current pattern is [[configuration][appender][rollingPolicy]] 16:13:23,158 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@26:24 - no applicable action for [fileNamePattern], current pattern is [[configuration][appender][rollingPolicy][fileNamePattern]] 16:13:23,159 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@27:17 - no applicable action for [minIndex], current pattern is [[configuration][appender][rollingPolicy][minIndex]] 16:13:23,159 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@28:17 - no applicable action for [maxIndex], current pattern is [[configuration][appender][rollingPolicy][maxIndex]] 16:13:23,159 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@31:85 - no applicable action for [triggeringPolicy], current pattern is [[configuration][appender][triggeringPolicy]] 16:13:23,160 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@32:20 - no applicable action for [maxFileSize], current pattern is [[configuration][appender][triggeringPolicy][maxFileSize]] <configuration> <contextName>Test</contextName> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>${JBOSS_HOME}/server/default/log/myApp.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>myApp.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>5</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1KB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%date %contextName %level [%thread] %logger{36} [%file:%line] %msg%n</pattern> </encoder> </appender> <logger name="com.test.logback" level="DEBUG" /> <root level="debug"> <appender-ref ref="FILE" /> <appender-ref ref="STDOUT" /> </root> </configuration> Nadia

1 0

Prudent mode logging to NFS-mounted file
by ThomasSchuessler2＠Eaton.com 21 Dec '11

21 Dec '11

We seem to be losing quite a few log records in a clustered web application writing to an NFS-mounted file with the configuration shown below. We are running logback-1.0.0. Any suggestions? <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <prudend>true</prudend> <encoder> <pattern>%d ${HOSTNAME} [%t] %-5p %c - {%marker} %m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <maxHistory>10</maxHistory> <fileNamePattern>/xxx/log-%d.log</fileNamePattern> </rollingPolicy> </appender> --------------------------------------------------------------------------

2 1

log rollover using %d multiple times in file name pattern?
by Thomas Corte 21 Dec '11

21 Dec '11

Hello, I'm trying to configure a log rollover with logs being *rolled daily* and put into a directory named "yyyy-MM", i.e. one folder for each *month* containing that month's logs. I'm using the following appender config: <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>app.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern%d{yyyy-MM}/app.%d{yyyy-MM-dd}.log</fileNamePattern> </rollingPolicy> <encoder> <pattern>%d{"yyyy-MM-dd HH:mm:ss,SSS"} [%thread] %-5level %logger{36} - %msg%n%xEx</pattern> </encoder> </appender> However, it seems as if the current logback implementation merely considers the first %d specification, which leads to a log rotation only once per month instead of the desired once per day frequency. I figure this is because via %d, the log rotation frequency and the file name pattern are somewhat tied together and seemingly can't be specified independently. Is there any way to achieve what I'm trying to do without writing custom code? Best regards, Thomas -- Thomas Corte Thomas.Corte(a)knipp.de

2 4

logback database appender
by Nadia Kunkov 20 Dec '11

20 Dec '11

Quick question - does logback database appender work only with the 3 pre-defined tables? I would like to log to my own tables that have different structure. Is it possible to do? Thanks so much! Nadia

1 0

Some logback-access questions
by Mike Wartes 20 Dec '11

20 Dec '11

Hello, I've been trying out the logback-access module as a potential replacement for Tomcat's AccessLogValve. I've run into a couple of issues that I'm wondering if anyone can help with. 1. It doesn't look like logback-access has the ability to print the query string like the %q value of Tomcat's AccessLogValve does. Am I missing something, or are there any workarounds? Unfortunately this is actually a dealbreaker for me if I can't make it work, since I need to have query strings in my access logs. 2. This one isn't a dealbreaker, but I'd like to configure one access log per webapp in my Tomcat container instead of one access log for all webapps. My first thought was that it'd be simple enough to configure the LogbackValve under each webapp's Context instead of under the Host element like the documentation suggests. However, I got stuck because of the way the LogbackValve is looking up its configuration file. I can't put the logback-access file in the container's conf directory because I want separate configuration per webapp. I also can't specify a relative path to the right webapp's folder because it can be in different places in different environments (the webapp files might not be in the container's folder at all). If I could look the configuration file up on the classpath I think that'd be pretty ideal, but from what I can tell it doesn't seem like that's possible. Any suggestions? I'm loving logback-classic and was excited to see that there is a module for access logs as well, but for the time being I think I may have to go back to the AccessLogValve. Thanks in advance.

2 2

starting with log back
by Nadia Kunkov 20 Dec '11

20 Dec '11

Hello, I'm trying to start off with logback but I'm having some silly problems. In the chapter2 it states: First, copy logback-audit/audit-server-generator/ folder which ships with logback-audit to a directory of your choice I can't find this generator in the distribution.... Also, I don't use maven - I use ant. Is there a quick way to set this up with Ant? Appreciate your help! Nadia

2 2

User-filtered logging - can be done?
by Y M 20 Dec '11

20 Dec '11

Hello, I'm trying to obtain a certain logging configuration, but so far I'm unsuccessful. I've read through the Logback manual, but I don't know if I can do what I want. It is a web application, and my objective is to enable a finer logging level for specific users, getting written to a specific log file, allowing better debugging directly in production environment. When needed, someone will set a tuned XML config using JMX to enable logging for the duration of the tests/data gathering (JMX is working fine). This is the relevant part of my logback.xml file: <configuration debug="true"> ... <appender name="FILTERED" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="com.sample.project.UserFilter">  <level>DEBUG</level> <user>123456</user> </filter> ... </appender> <logger name="com.sample.project"> <appender-ref ref="FILTERED" /> </logger> <logger name="com.sample.legacy" additivity="false"> <appender-ref ref="LEGACY" /> </logger> <root level="WARN"> <appender-ref ref="STANDARD" /> </root> </configuration> With this config, I intend to have:- WARN+ level at root;- events from legacy project tree only on 'LEGACY' (working fine);- 'FILTERED' logging only DEBUG+ events from user '123456' under 'com.sample.project', while its level ramains at WARN (not OK). Sample:getLogger("com.sample.abc").warn("..."); //logged to STANDARDgetLogger("com.sample.abc").debug("..."); //not loggedgetLogger("com.sample.legacy").warn("..."); //logged to LEGACYgetLogger("com.sample.project").warn("..."); //logged to STANDARD; also logged to FILTERED if user is 123456getLogger("com.sample.project").debug("..."); //logged to FILTERED if user is 123456 As I tested, a 'logger.debug()' from the desired user does not get logged, the filter is not even called, and I suspect that the effective WARN level denies the event before reaching my filter (I hoped for the other way around). If I set DEBUG on 'com.sample.project', 'FILTERED' will get the correct logging, but 'STANDARD' will be flooded with DEBUG+ logging from 'com.sample.project'. And disabling additivity on it removes all logging belonging to this hierarchy from 'STANDARD'. So, I see Logback is working properly, my desired logging seems to be against the standard architecture. But is there a way to archive the described effect?I was thinking of a TurboFilter, allowing lower level events from selected users (not tested yet), but I'm not sure the effective level would kick in first, also it wouldn't do the desired logging separation between 'STANDARD' and 'FILTERED' anyway. As another approach, maybe this would require a custom Logger class, handling specific appenders in a special way. Unfortunately, I have no idea if I can plug in custom Loggers, and also not sure how to code it (Logger class source is quite complex in a quick look). Sorry if it wasn't clear, I'm not sure how to present the situation. I can provide further details, if needed.Any help is welcome. If someone could show me which way to follow, maybe classes or methods to extend, I'd be grateful. Many thanks!

3 6

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 09.01.2012)
by manfred.kuhlmann＠steria-mummert.de 19 Dec '11

19 Dec '11

Ich werde ab dem 18.12.2011 nicht im Büro sein. Ich kehre zurück am 09.01.2012. I will be out of the office starting 18.12.2011. I will be back on 09.01.2012. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. I will answer your message after my return. Bitte Ihre Ansprechpartner in der Mitarbeiterdatenbank unter dem Reiter 'Abwesenheitsvertreter' eingeben (s.a. Hilfe-Button). Mit freundlichen Grüßen Best regards Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " [logback-user] Problems with DBAppender / JNDI / JBoss 7 / OracleDB" gesendet am 19.12.2011 16:31:39. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. Steria Mummert Consulting AG Vorsitzender des Aufsichtsrates: Jürgen Sponnagel - Vorstand: Oliver Nazet (Vors.), Dr. Reinhard Liedl, Dr. Fritz Moser Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351 Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2 pro Seite. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie, den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden können. This e-mail communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.

1 0