December 2010 - logback-dev

[JIRA] Created: (LBACCESS-19) Cannot specify config file relative to catalina home
by Eric Estievenart (JIRA) 06 Dec '10

06 Dec '10

Cannot specify config file relative to catalina home ---------------------------------------------------- Key: LBACCESS-19 URL: http://jira.qos.ch/browse/LBACCESS-19 Project: logback-access Issue Type: Bug Affects Versions: 0.9.26 Environment: all Reporter: Eric Estievenart Assignee: Logback dev list Priority: Trivial There is no way to refer to catalina home when specifying the filename of a logback valve. What I would like to do is something like: <Valve className="ch.qos.logback.access.tomcat.LogbackValve" filename="${catalina.home}/conf/logback-access-test.xml" /> The only way for now is to specify an absolute path, which is not very convenient. The system properties in the filename should be expanded in LogbackValve.start(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 1

[JIRA] Created: (LBACCESS-20) [DOC] logback-access.html example uses obsolete <layout> in <appender> (in access.html)
by Eric Estievenart (JIRA) 06 Dec '10

06 Dec '10

[DOC] logback-access.html example uses obsolete <layout> in <appender> (in access.html) --------------------------------------------------------------------------------------- Key: LBACCESS-20 URL: http://jira.qos.ch/browse/LBACCESS-20 Project: logback-access Issue Type: Bug Affects Versions: 0.9.26 Environment: - Reporter: Eric Estievenart Assignee: Logback dev list Priority: Trivial http://logback.qos.ch/access.html, in example 1: <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.access.PatternLayout"> ------ should be ---------- <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> Cheers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

GEventEvaluator not started
by Markward Schubert 02 Dec '10

02 Dec '10

Hi! I am experiencing a problem with the GEventEvaluator. After hours of trying around with different configurations, I could not get this to work. The Filter was simply ignored. I even tried 1 == 2 as an expression, but it was happily logging. Finally I started my project in debugmode and startet stepping around the logback code. Now my question: Is it possible, that GEventEvaluator misses a call to super.start() in it's start-method? EvaluatorFilter in my case returns FilterReply.NEUTRAL in the code-passage below, as evaluator.isStarted() returns false. if (!isStarted() || !evaluator.isStarted()) { return FilterReply.NEUTRAL; } Regards, Markward

2 1