January 2008 - logback-user

auto context name creation
by Ingo Siebert 30 Jan '08

30 Jan '08

Hi, i switched to logback because it sounds promising. I have an web appplication (Tomcat6) which can be deployed more than once. In the FAQ i've read this to get a context-based logging. <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>ContextApp-A</env-entry-value> </env-entry> Is it possible to auto-create a different "ContextApp-A" value? Reason: I want to deploy nearly the same WAR under different names at the same time. Example: myApp22012008.war and myApp23012008.war Cheers, Ingo

2 2

Tomcat access logs
by whatever21 25 Jan '08

25 Jan '08

Hi, I'm having some problems getting Tomcat (version 6.0.14) access logs to work in conjunction with Logback and my other loggers. This is what my logback.xml looks like (its exploded into ../WEB-INF/classes/ when I deploy a new .war): <configuration debug="true">  <substitutionProperty name="logEng.log.dir" value="${base.log.dir}/loggingEngine"/> <substitutionProperty name="targeting.log.dir" value="${base.log.dir}/targeting"/> <substitutionProperty name="normalize.log.dir" value="${base.log.dir}/normalize"/> <substitutionProperty name="cookie.dir" value="/home/tomcat/globalHistory"/> <appender name="LOGGINGENGINE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logEng.log.dir}/logEng.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern> logEng-%d{yyyy-MM-dd}.log.gz </FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %d{yyyy/MM/dd HH:mm:ss ZZZ}\t%msg%n </Pattern> </layout> </appender> <appender name="TARGETING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${targeting.log.dir}/targeting.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern> targeting-%d{yyyy-MM-dd}.log.gz </FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %d{yyyy/MM/dd HH:mm:ss ZZZ}\t%msg%n </Pattern> </layout> </appender> <appender name="NORMALIZE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${normalize.log.dir}/normalize.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern> normalize-%d{yyyy-MM-dd}.log.gz </FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %msg%n </Pattern> </layout> </appender> <appender name="COOKIE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${cookie.dir}/cookie.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern> cookie-%d{yyyy-MM-dd}.log.gz </FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %msg%n </Pattern> </layout> </appender> <logger name="CookieLog" additivity="false"> <level value="INFO"/> <appender-ref ref="COOKIE"/> </logger> <logger name="TargetingLog" additivity="false"> <level value="ALL"/> <appender-ref ref="TARGETING"/> </logger> <logger name="NormalizeLog" additivity="false"> <level value="ALL"/> <appender-ref ref="NORMALIZE"/> </logger> <root> <level value="ALL"/> <appender-ref ref="LOGGINGENGINE"/> </root> </configuration> My logback configuration works like a charm but I get no access logs under TOMCAT_HOME/logs Under TOMCAT_HOME/lib/ I have the usual jars and I've added: logback-access-0.9.8.jar logback-core-0.9.8.jar What should I have under ../WEB-INF/lib/? I don't have much experience with logging in general (which is probably apparent :) Thanks, Jennifer -- View this message in context: http://www.nabble.com/Tomcat-access-logs-tp14946148p14946148.html Sent from the Logback User mailing list archive at Nabble.com.

2 4

no log messages after redeployment
by Ingo Siebert 25 Jan '08

25 Jan '08

Hi, I use the JNDI switch for logback. If I undeploy my application, the old JNDI context ist destroyed. That's fine. But I redeploy the same application with the same context name, no logging messages are displayed. If I restart Tomcat6 and the deployed application comes up, i see the messages again. The libs which are needed by my application are stored in the tomcat6/sharedLib folder. Any idea why the messages are missing? Ingo This is my web.xml: <filter> <filter-name>LoggerContextFilter</filter-name> <filter-class>ch.qos.logback.classic.selector.servlet.LoggerContextFilter</filter-class> </filter> <filter-mapping> <filter-name>LoggerContextFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener>  <listener> <listener-class>ch.qos.logback.classic.selector.servlet.ContextDetachingSCL</listener-class> </listener> ... <env-entry> <description>JNDI logging context for this app</description> <env-entry-name>logback/context-name</env-entry-name> <env-entry-value>EIMContext-1</env-entry-value> <env-entry-type>java.lang.String</env-entry-type> </env-entry> <env-entry> <description>URL for configuring logback context</description> <env-entry-name>logback/configuration-resource</env-entry-name> <env-entry-value>eim_logback.xml</env-entry-value> <env-entry-type>java.lang.String</env-entry-type> </env-entry>

1 0

ContextJNDISelector is only called once
by Ingo Siebert 23 Jan '08

23 Jan '08

Hi, if set logback to JNDI and put all logback and slf4j libs in tomcat6/lib directory. If i deploy the same WAR, with a different name and context-name in the web.xml, twice, the ContextJNDISelector is only called once. That results in that the second WAR uses the logback config of the first WAR. Any idea why ContextJNDISelector is only called once? The problem is even more serious. If u undeploy the first WAR, the JNDI-context is removed. But if i redeploy the first WAR again, i get no log messages at all, because ContextJNDISelector isn't called again. I don't know how to proceed. Any idea? Cheers, Ingo

1 0

Is there System properties configuration?
by thebugslayer 15 Jan '08

15 Jan '08

Hi, I read http://logback.qos.ch/manual/joran.html, it's only checking classpath for config logback.xml file. Is there a way to specify file location by System properties? Thanks, -- /bugslayer

5 8

logback and Jetty
by whatever21 15 Jan '08

15 Jan '08

I have a test environment where I'm running a tomcat server and logback, and everything works beautifully, where the various loggers are outputting to the right directories specified in my logback.xml. Trying to use the same configuration file and code, but with a Jetty server, is not working at all. I've tried putting logback.xml in various places like, WEB-INF/resources/, WEB-INF/src/, $JETTY_HOME/etc/, $JETTY_HOME/bin/...All with no luck. I've also tried explicitly specifying the file in jetty.xml with the same results. Not sure where I'm going wrong. Any suggestions? What jar's should I have under $JETTY_HOME/lib/? How can I make jetty server logs work alongside logback? Thanks. -- View this message in context: http://www.nabble.com/logback-and-Jetty-tp14818796p14818796.html Sent from the Logback User mailing list archive at Nabble.com.

2 1

recreate deleted file
by Will Norris 10 Jan '08

10 Jan '08

Are any of the logback FileAppenders able to recreate their logfile if it goes away for whatever reason. In my testing, if I delete the log file or move it to another location, logback doesn't log any futher until I restart my application. I would like for it to recreate the file if it is no longer present. Is that possible? Thanks, Will

3 3

Manfred Kuhlmann is out of office.
by Manfred.Kuhlmann＠steria-mummert.de 03 Jan '08

03 Jan '08

Ich werde ab dem 27.12.2007 nicht im Büro sein. Ich kehre zurück am 04.01.2008. I will be out of the office starting 27.12.2007. I will be back on 04.01.2008. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. I will answer your message after my return. Mit freundlichen Grüßen Best regards Manfred Kuhlmann

1 0