- logback-dev - mailman3.qos.ch

Logback 0.9.12 ?
by Szel, Zoltan (IT) 04 Dec '08

04 Dec '08

Hi all, i would like to ask when Logback 0.9.12 is going to be released? Thank in advance, Best Regards, Zoltan Szel -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.

3 8

[JIRA] Commented: (LBCLASSIC-43) Application name for a web-app
by Ceki Gulcu (JIRA) 03 Dec '08

03 Dec '08

[ http://jira.qos.ch/browse/LBCLASSIC-43?page=com.atlassian.jira.plugin.syste… ] Ceki Gulcu commented on LBCLASSIC-43: ------------------------------------- There are several ways to read this issue. One, is to add an HttpServletFilter for invoking MDC.put("applicationName","whatever") which seems noisy. Anothtr way to look at this, is to to set the name of the logger context from a configuration file. For example, <configuration contextName="whatever">...</configration> > Application name for a web-app > ------------------------------ > > Key: LBCLASSIC-43 > URL: http://jira.qos.ch/browse/LBCLASSIC-43 > Project: logback-classic > Issue Type: Improvement > Components: Other > Affects Versions: unspecified > Environment: Operating System: Windows > Platform: PC > Reporter: Ceki Gulcu > Assignee: Logback dev list > Priority: Minor > > Logback should provide support for setting the application name of a web-app (or a JEE application) out of the box. The LoggingContext is a good place for this. > See also: > http://www.qos.ch/pipermail/logback-user/2008-March/000400.html -- 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

[JIRA] Created: (LBGENERAL-25) New XML Appender
by Greg (JIRA) 03 Dec '08

03 Dec '08

New XML Appender ---------------- Key: LBGENERAL-25 URL: http://jira.qos.ch/browse/LBGENERAL-25 Project: logback-general Issue Type: New Feature Affects Versions: 0.9.12 Environment: Any Reporter: Greg Assignee: Logback dev list As suggested by Thorbjorn Ravn Andersen (http://www.nabble.com/Logback-or-Log4J-Servers-and-Log4Cxx-client-td2060862…) I'd like to suggest an "upgrade" to the logback service. It would be great if the logback had an appender which can push log events over the network in an XML format. Since I really, really need to have a server that accepts log from C++ and Java clients, this would be a perfect solution to my problem. The Short or the Simple server could accept logs in such a format, which also means other than C++ or Java clients could write logs to the Loback server etc. Is it possible for you guys to implement both the client and the server appender that sends and accepts log in a plain XML format? Big thanks. -- 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

[JIRA] Closed: (LBCLASSIC-40) Dynamically setting the log levels from a unit test
by Ceki Gulcu (JIRA) 03 Dec '08

03 Dec '08

[ http://jira.qos.ch/browse/LBCLASSIC-40?page=com.atlassian.jira.plugin.syste… ] Ceki Gulcu closed LBCLASSIC-40. ------------------------------- > Dynamically setting the log levels from a unit test > --------------------------------------------------- > > Key: LBCLASSIC-40 > URL: http://jira.qos.ch/browse/LBCLASSIC-40 > Project: logback-classic > Issue Type: Improvement > Components: Other > Affects Versions: unspecified > Environment: Operating System: Other > Platform: PC > URL: http://www.jroller.com/robwilliams/entry/classes_for_using_logs_in > Reporter: Ceki Gulcu > Assignee: Logback dev list > Priority: Minor > > Rob's idea has merit. We should look into it. -- 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

[JIRA] Resolved: (LBCLASSIC-40) Dynamically setting the log levels from a unit test
by Ceki Gulcu (JIRA) 03 Dec '08

03 Dec '08

[ http://jira.qos.ch/browse/LBCLASSIC-40?page=com.atlassian.jira.plugin.syste… ] Ceki Gulcu resolved LBCLASSIC-40. --------------------------------- Resolution: Won't Fix > Dynamically setting the log levels from a unit test > --------------------------------------------------- > > Key: LBCLASSIC-40 > URL: http://jira.qos.ch/browse/LBCLASSIC-40 > Project: logback-classic > Issue Type: Improvement > Components: Other > Affects Versions: unspecified > Environment: Operating System: Other > Platform: PC > URL: http://www.jroller.com/robwilliams/entry/classes_for_using_logs_in > Reporter: Ceki Gulcu > Assignee: Logback dev list > Priority: Minor > > Rob's idea has merit. We should look into it. -- 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

[JIRA] Closed: (LBCLASSIC-42) Multiple applications sharing the same config file
by Ceki Gulcu (JIRA) 03 Dec '08

03 Dec '08

[ http://jira.qos.ch/browse/LBCLASSIC-42?page=com.atlassian.jira.plugin.syste… ] Ceki Gulcu closed LBCLASSIC-42. ------------------------------- > Multiple applications sharing the same config file > -------------------------------------------------- > > Key: LBCLASSIC-42 > URL: http://jira.qos.ch/browse/LBCLASSIC-42 > Project: logback-classic > Issue Type: Improvement > Components: Other > Affects Versions: unspecified > Environment: Operating System: Windows > Platform: PC > URL: http://marc.info/?t=120308330000003&r=1&w=2 > Reporter: Ceki Gulcu > Assignee: Ceki Gulcu > Priority: Minor > Fix For: 0.9.12 > > > The idea is to have a number of applications (over 20) to share the same config file so that the log output goes to different files. -- 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

[JIRA] Resolved: (LBCLASSIC-42) Multiple applications sharing the same config file
by Ceki Gulcu (JIRA) 03 Dec '08

03 Dec '08

[ http://jira.qos.ch/browse/LBCLASSIC-42?page=com.atlassian.jira.plugin.syste… ] Ceki Gulcu resolved LBCLASSIC-42. --------------------------------- Fix Version/s: 0.9.12 Resolution: Fixed Added an FAQ entry: Is it possible for multiple JEE applications to share the same configuration file but without stepping on each other's toes? > Multiple applications sharing the same config file > -------------------------------------------------- > > Key: LBCLASSIC-42 > URL: http://jira.qos.ch/browse/LBCLASSIC-42 > Project: logback-classic > Issue Type: Improvement > Components: Other > Affects Versions: unspecified > Environment: Operating System: Windows > Platform: PC > URL: http://marc.info/?t=120308330000003&r=1&w=2 > Reporter: Ceki Gulcu > Assignee: Ceki Gulcu > Priority: Minor > Fix For: 0.9.12 > > > The idea is to have a number of applications (over 20) to share the same config file so that the log output goes to different files. -- 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

svn commit: r2049 - in logback/trunk/logback-site/src/site/pages: . manual
by noreply.ceki＠qos.ch 03 Dec '08

03 Dec '08

Author: ceki Date: Wed Dec 3 19:18:33 2008 New Revision: 2049 Modified: logback/trunk/logback-site/src/site/pages/faq.html logback/trunk/logback-site/src/site/pages/manual/joran.html logback/trunk/logback-site/src/site/pages/news.html Log: Added an FAQ entry: Is it possible for multiple JEE applications to share the same configuration file but without stepping on each other's toes? Related to LBCLASSIC-42 Modified: logback/trunk/logback-site/src/site/pages/faq.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/faq.html (original) +++ logback/trunk/logback-site/src/site/pages/faq.html Wed Dec 3 19:18:33 2008 @@ -45,6 +45,14 @@ <a href="#auto_config">How does the automatic configuration work?</a> </li> + + <li> + <a href="#sharedConfiguration">Is it possible for multiple JEE + applications to share the same configuration file but without + stepping on each other's toes? + </a> + </li> + <li> <a href="#setup_jetty">How can Jetty be instructed to use logback-classic as its logging implementataion? @@ -99,11 +107,11 @@ This question is answered in the <a href="manual/joran.html#auto_configuration">relevant section</a> of the logback manual. - - + + <hr/> </dd> - <hr/> +  @@ -122,9 +130,65 @@ <code>org.slf4j.LoggerFactory</code>. Thus, it is possible for a logback logger to be deserialized as a log4j or j.u.l. logger, depending on the deserialization environment. + + <hr/> + </dd> + + +  + + <dt> + <a name="sharedConfiguration" href="#sharedConfiguration"> + Is it possible for multiple JEE applications to share the + same configuration file but without stepping on each other's + toes?</a> + </dt> + <dd> + Yes, it is. Using <a + href="manual/joran.html#variableSubstitution">variable + substitution</a>, it is possible to have a single + configuration file to output logs to different destinations + depending on each JEE application. Here is a sample + configuration file designed for this purpose. + + <configuration> + <appender name="FILE" class="ch.qos.logback.core.FileAppender"> +  + <File>c:/logs/${application-name}.log</File> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%d %p %t %c - %m%n</Pattern> + </layout> + </appender> + <root level="debug"> + <appender-ref ref="FILE"/> + </root> +</configuration> + + Assuming each JEE application loads a different copy of + logback classes into memory, if we can somehow inject a + different value for <code>application-name</code> + each time an application starts, logs will be output to + different files. We just need to initialize logback with the + above configuration file while injecting a different value + for <code>application-name</code> variable. Here is + sample code that programmatically configures logback. It + should be invoked during the initialization of your JEE + applications. + + + LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); + // inject the name of the current application as "applicaiton-name" + // property of the LoggerContext + context.putProperty("application-name", NAME_OF_CURRENT_APPLICATION); + JoranConfigurator jc = new JoranConfigurator(); + jc.setContext(context); + context.reset(); // override default configuration + jc.doConfigure("/path/to/the/above/configuration/file.xml"); + + <hr/> </dd> - <hr/> +  <dt> @@ -139,31 +203,34 @@ logging. - The following jar files must be present in the - JETTY_HOME/lib directory. + Logback jar files must be present on Jetty's class + path. These files are + logback-core-${project.version}.jar and + logback-classic-${project.version}.jar. These files + should be placed under the $JETTY_HOME/lib + directory. + + + Since Jetty's uses an older version of SLF4J internally, + we recommend that the old version be replaced by + slf4j-api-${slf4j.version}.jar. This file can be + downloaded from the <a + href="http://www.slf4j.org/download.html">SLF4J</a> project. + + - Logback-classic is based on the SLF4J api. Therefore, the - slf4j-api-VERSION.jar jar must be present. This jar - can be downloaded from the <a - href="http://www.slf4j.org/">SLF4J</a> project. - - Logback's own jars must also be present, namely - logback-core-VERSION.jar and - logback-classic-VERSION.jar . - - - To configure logback-classic, a file called - logback.xml should be placed in the - JETTY_HOME/resources directory. You can find sample - configuration files in the - logback-examples/src/main/java/chapter4/conf/ folder - shipping within the logback distribution. + For automaticly configuring logback-classic, you can + place the file logback.xml under the + $JETTY_HOME/resources directory. You can find + sample configuration files in the + logback-examples/src/main/java/chapter4/conf/ + folder shipping within the logback distribution. + <hr/> </dd> - <hr /> Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/joran.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/joran.html Wed Dec 3 19:18:33 2008 @@ -954,7 +954,8 @@ foo.log file and only in that file. - <h4>Variable substitution</h4> + <h4><a name="variableSubstitution" + href="#variableSubstitution">Variable substitution</a></h4> In principle, variable substitution can occur at any point where a value can be specified. The syntax of variable substitution is @@ -1133,7 +1134,9 @@ </root> </configuration></pre></div> - <h4>Default substitution values for variables</h4> + <h4><a name="defaultValuesForVariables" + href="#defaultValuesForVariables">Default substitution values for + variables</a></h4> Under certain circumstances, it may be desirable for a variable to have a default value in case it is not declared or its value is Modified: logback/trunk/logback-site/src/site/pages/news.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/news.html (original) +++ logback/trunk/logback-site/src/site/pages/news.html Wed Dec 3 19:18:33 2008 @@ -28,7 +28,7 @@ <hr width="80%" align="center" /> - <h3>28th of November 2008 - Release of version 0.9.12</h3> + <h3>4th of December 2008 - Release of version 0.9.12</h3> Fixed <a href="http://jira.qos.ch/browse/LBCORE-26">bug LBCORE-26</a> reported by Tsutomu YANO and independently by @@ -59,7 +59,13 @@ href="http://jira.qos.ch/browse/LBCLASSIC-33">LBCLASSIC-33</a>, <a href="http://jira.qos.ch/browse/LBCLASSIC-14">LBCLASSIC-24</a> and <a href="http://jira.qos.ch/browse/LBCLASSIC-24">LBCLASSIC-14</a> - JMXConfigurator has been redesigned. + <code>JMXConfigurator</code> has been redesigned. + + + Fixed <a + href="http://jira.qos.ch/browse/LBGENERAL-22">LBGENERAL-22</a>. The + <a href="http://logback.qos.ch/translator/">log4j.properties + translator</a> web-application has been significatnly refactored. Fixed improvement request <a

1 0

[JIRA] Created: (LBCLASSIC-73) LevelFilter should not match exact filter, but greaterOrEqual
by Bruno Navert (JIRA) 03 Dec '08

03 Dec '08

LevelFilter should not match exact filter, but greaterOrEqual ------------------------------------------------------------- Key: LBCLASSIC-73 URL: http://jira.qos.ch/browse/LBCLASSIC-73 Project: logback-classic Issue Type: Improvement Components: appender Affects Versions: 0.9.9 Reporter: Bruno Navert Assignee: Logback dev list Priority: Minor LevelFilter currently matches EXACT level, it would be useful to match on greaterOrEqual instead. This would allow setting filter to DEBUG for instance, and it would allow INFO,ERROR etc through -- 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

2 3

[JIRA] Resolved: (LBCLASSIC-29) Improve logging message of ContextJNDISelector
by Ceki Gulcu (JIRA) 03 Dec '08

03 Dec '08

[ http://jira.qos.ch/browse/LBCLASSIC-29?page=com.atlassian.jira.plugin.syste… ] Ceki Gulcu resolved LBCLASSIC-29. --------------------------------- Fix Version/s: 0.9.12 Resolution: Fixed Fixed in revision 2034. See also http://tinyurl.com/6cue9x > Improve logging message of ContextJNDISelector > ---------------------------------------------- > > Key: LBCLASSIC-29 > URL: http://jira.qos.ch/browse/LBCLASSIC-29 > Project: logback-classic > Issue Type: Improvement > Components: Other > Affects Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Sebastian Davids > Assignee: Logback dev list > Priority: Minor > Fix For: 0.9.12 > > > 14:08:09.153 [main] WARN root - The provided URL for contextmyContextName does not lead to a valid file > First, there is a missing space between context and its name, second you should show which URL has been provided, e.g.: > 14:08:09.153 [main] WARN root - The provided URL 'my/url/' for context myContextName does not lead to a valid file > @@@@ > Reproduce: http://logback.qos.ch/manual/contextSelector.html > <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>myContextName</env-entry-value> > </env-entry> > <env-entry> > <description>URL for configuring logback context</description> > <env-entry-name>logback/configuration-resource</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <env-entry-value>unknown.url</env-entry-value> > </env-entry> -- 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