- logback-dev - mailman3.qos.ch

svn commit: r1257 - logback/trunk/logback-site/src/site/xdocTemplates
by noreply.seb＠qos.ch 19 Jan '07

19 Jan '07

Author: seb Date: Fri Jan 19 18:33:53 2007 New Revision: 1257 Modified: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Log: Updates on the demo doc Modified: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/demo.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Fri Jan 19 18:33:53 2007 @@ -17,9 +17,9 @@ - First, please download the logback demo. You will need a + First, please download the logback demo. You will need to install a <a href="http://subversion.tigris.org/">Subversion</a> client - and issue the following command: + and issue the following command in a command/terminal window: <div class="source"><pre>svn co http://svn.qos.ch/repos/logback-demo logback-demo</pre></div> @@ -34,14 +34,14 @@ - Using Maven, let's run the demo for the first time. From the logback-demo - directory, issue the following command: + Using Maven, let's package the files and run the demo for the first time. + From the logback-demo directory, issue the following command: -<div class="source"><pre>mvn jetty:run</pre></div> +<div class="source"><pre>mvn package jetty:run</pre></div> - Then, visit http://localhost:8080/ to view the main page of the logback demo. + Then, visit http://localhost:8080/logback-demo/ to view the main page of the logback demo. image main page @@ -50,17 +50,18 @@ For now, logback uses two components: one <code>ConsoleAppender</code> and one <code>RollingFileAppender</code>. The <code>RollingFileAppender</code> sends logging events to a file called logFile.log and will rollover -the active file every minute. The old file will be renamed and compressed using the zip -format. The <code>ConsoleAppender</code> will output the logging requests to the console, +the active file every minute. The old file will be renamed and compressed to zip +file. The <code>ConsoleAppender</code> will output the logging requests to the console, and shorten the logger names to gain some space in the console window, without making the names unreadable. You can study the configuration file that is used by editing the file called logback.xml, located in the src/main/resources/ directory -of the demo. +of the demo. You might want to keep this file in an editor window, since we will +modify its content several times thoughout the demo. Let's now visit the ViewStatii page, via the navigation menu on the left hand -of the screen. This page contains the content of the <code>Status</code> objects that were +of the navigator window. This page contains the content of the <code>Status</code> objects that were created until now. <code>Status</code> objects are a part of logback's powerful internal reporting framework. They allow you to see what is going on in logback, and check that a configuration file has been parsed correctly, or that a rollover has occured as @@ -72,19 +73,23 @@ Visiting the View logs page does not impress much at the moment. Let us uncomment the two parts of the config file that are below the Part I: Cyclic buffer comment. +A <code>CyclicBuffer</code> is a class that keeps track of logging events and holds these +objects for immediate or differed display. Now reload the web-app by exiting the previous command with CTRL-C and issuing it -again: mvn jetty:run. +again: mvn package jetty:run. Now, the View logs page looks prettier. By virtue of the <code>CyclicBufferAppender</code>, this page can fetch the last events and present them through a servlet. We see that each 3 seconds -a line is added to the logs. +a line is added to the logs. The formatting of this page is made with +a <code>HTMLLayout</code>. This component creates a nice readable table containing the logging +events, based on a pattern that describes the information one wants to see in the table. Having the logs that we see on the web page cluttered with scheduled messages -is not very comfortable. To get rid of these logs once we've verified that they +is not very comfortable. To get rid of these logs, now that we've verified that they work, we can add an <code>EvaluatorFilter</code> to the Appender. Uncomment the parts named PART II: Cyclic buffer with Evaluator. You may then comment or delete the first Basic Cyclic buffer elements. @@ -105,8 +110,15 @@ </filter></pre></div> -The expression element contains a familiar java statement. It uses a few variables -that are made available by logback before the filter evaluates the expression. +The expression element contains a familiar java statement. This expression +checks that the name of the logger contains the String LoggingTask, but +also that the message accompagnying the log contains Howdydy-diddly-ho. +Moreover, in order to be sure that the Howdydy-diddly-ho task actually +works, we add to the expression a last statement that allows logs to be processed +for the first 20 seconds after the application launch. +The variables used in this statement (<code>logger</code>, <code>message</code> and +<code>event</code>) are made available by logback before the filter +evaluates the expression. The OnMatch element allows the user to choose the filter's behaviour once the expression was evaluated to true. A similar OnMismatch element exists. @@ -119,7 +131,8 @@ Logback ships with a special category of filters: <code>TurboFilter</code> objects are ultra-fast, context-wide filters. They reveals themselves very useful to -test MDC values, for examples. Let's uncomment the part named +test MDC values, for examples and to add context-wide conditions to allow or deny +logging events. Let's uncomment the part named PART III: TurboFilter: MDC value in the logback.xml file. @@ -129,16 +142,79 @@ associated with a MDC value of sebastien bound to the username key. -To view the consequences of such a <code>TurboFilter</code>, try to log in the -application using the username sebastien, perform some tasks, log out -and log in again using another username. The View logs page should -clearly mark the difference between the logs that were generated when the first -and second user were logged in. +To view the consequences of such a <code>TurboFilter</code>, we are going to +stop all logging activity, except for a specific user. To achieve that, the simplest +way is to set the root logger's level to <code>OFF</code>. Modify the level +element, nested inside the root element of logback.xml. Its value +attribute should be OFF instead of DEBUG. Next, restart the server +as we've done previously. + +Once on the demo main webpage again, perform a few actions (i.e. calculate +a few prime numbers) and watch the View logs page. The table should be +empty. + + + +Now log in the application using the username sebastien and perform a few +prime calculations again. The View logs page now shows the logs that were +generated by the calculation classes. Moreover, each log is associated with the name +of the user who provoked the logging event. Please log off before continuing the +demo, using the logout button on the left. + + + +Parametrized logging is a feature that will be a great asset for any performance-critical +system. Usually, a logging request is issued like this: + + +<div class="source"><pre>logger.debug("Hello, my name is" + username + ", I am " + age + " years old.");</pre></div> + + +By issuing this line, the cost of constructing the String cannot be saved when the +log request is not processed. For example, using the <code>debug()</code> method +when, as we've just done, the root level is any value higher that DEBUG will +result in a loss of time because all calls to the <code>debug()</code> method will +be eventually dropped. + + + +Logback offers the following method: + + +<div class="source"><pre>logger.debug("Hello, my name is {}, I am {} years old", username, age);</pre></div> + + +As you can see, the variables are not inserted in the message yet. Both the message +and the values will be saved and used later, if the logging event is processed. + + + +Let us now run a test to see what kind of gain can we expect from this different +message formatting approach. First, go to the Prime number page and +run a few calculations. Check the time it takes to compute the results. To +see a clearer difference between the two formatting methods, you might want to +try the two big integers that are listed below the prime number textbox. + -Part IV? Parametrized logging: modify source? +Now let us edit the <code>NumberCruncherImpl</code> class, to switch the log methods. +You will find this class in the src/main/java/ch/qos/logback/demo/prime/ +directory. On line 54 and 55, just umcomment the parametrized logging line and +and comment out the other line. Restart the server with mvn package jetty:run +and re-run the calculations you tried beforehand. + + + +The durations should be obviously different. Remember that we had turned off all +logging in the previous step of this demo. With the initial formatting method, +we were constructing the logging message ("Trying "+i+" as a factor.") +a huge amount of time, actually each time a factor was tried for these big numbers. +With the paramatrized logging, the construction of the message was postponed and, since +logging was turned off, not processed. We see here that the cost of the non-logging +was taken down to a very small figure, dividing the total cost of the calculation +by a non-negligeable factor. @@ -245,22 +321,76 @@ -Part VIII: JMX for access and classic +Logback publishes several components via JMX. This allows you to see +the status of certain objects, and change several configuration parameters. + +To see logback access' components, visit the following page: + +<div class="source"><pre>http://localhost:8082/</pre></div> + +The domain ch.qos.logback.access.jetty contains an entry +that allows you to see the RequestLogImpl component. This component +is used to plug logback in Jetty's internal achitecture. Clicking on +it reveals the status of several parameters, such as the started status, and +two methods are available to start and stop the RequestLogImpl. + + +To see the influence of the available operations, place the terminal window +and your web browser such that you can see them both. Stop the RequestLogImlp +and reload a few times the main page of the demo. Nothing should be displayed. If you start +the RequestLogImpl again, the requests will be shown in the terminal +window. + + +These is more to discover with logback and JMX. In the logback.xml file, +placed in the src/main/resources directory, uncomment the <code>JMXConfigurator</code> +element. Once done, restart the server. + + +By refreshing the loaded previously JMX page, you should see a new component, +under the domain ch.qos.logback.classic. It is the <code>JMXConfigurator</code>. +Clicking on it reveals its content. Its possibilities are listed below: + +<ul> + + Reload the configuration using the same file that was + previously used. + + + Reload the configuration using a file whose path is passed as + a parameter. + + + Reload the configuration using a file whose URL is passed as a + parameter. + + Get the level of a logger + Change the level setting of a specified logger. + Change a list of all declared loggers. + Change the level setting of a specified logger. +</ul> + + In the last case, you must specify the name of the logger you + wish to alter, and its new level. + + +Let us test the configurator. If you try to use the Prime Number page and +look at the View logs page after, you should see two types of logs. When the +calculation checks if a number is a factor, a DEBUG log is displayed. When +the calculation has found a factor, a INFO log is displayed. If you set the level +of the ch.qos.logback.demo.prime logger to INFO, and run a prime calculation +again, you should not see the DEBUG level logs anymore. + - - - - - - </body> +</body> </document> \ No newline at end of file

1 0

svn commit: r1256 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 19 Jan '07

19 Jan '07

Author: seb Date: Fri Jan 19 12:07:07 2007 New Revision: 1256 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml Log: Updated doc on response converters Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml Fri Jan 19 12:07:07 2007 @@ -1672,6 +1672,31 @@ </td> </tr> + <tr> + <td align="center">responseContent</td> + <td> + + This conversion word displays the content of the response, that is the + response's <code>InputStream</code>. It is used in conjunction with a + <a href="../xref/ch/qos/logback/access/servlet/TeeFilter.html"> + <code>TeeFilter</code></a>, a <code>javax.servlet.Filter</code> that + replaces the original <code>HttpServletResponse</code> + by a <a href="../xref/ch/qos/logback/access/servlet/TeeHttpServletResponse.html"> + <code>TeeHttpServletResponse</code></a>. The latter object allows + access to the requet's <code>InputStream</code> multiple times without + any loss of data. + + </td> + </tr> + <tr> + <td align="center">fullResponse</td> + <td> + + This conversion word takes all the available headers of the + response and displays their values. + + </td> + </tr> </table> Logback access' <code>PatternLayout</code> also recognize three keywords, which

1 0

[continuum] BUILD FAILURE: Logback Access Module
by John Noreplai 19 Jan '07

19 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Failed Started at: Fri, 19 Jan 2007 10:02:08 +0100 Finished at: Fri, 19 Jan 2007 10:02:23 +0100 Total time: 14s Build Trigger: Forced Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Access Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 64 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] [retrotranslator:translate {execution: default}] [INFO] Transforming 80 file(s) from /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/logback-access-0.8.1-SNAPSHOT-jdk14.jar. [INFO] Transformation of 80 file(s) completed successfully. [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.access.db.DBAppenderTest [Server@7bd63e39]: [Thread[main,5,main]]: checkRunning(false) entered [Server@7bd63e39]: [Thread[main,5,main]]: checkRunning(false) exited [Server@7bd63e39]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@7bd63e39]: [Thread[main,5,main]]: checkRunning(false) entered [Server@7bd63e39]: [Thread[main,5,main]]: checkRunning(false) exited [Server@7bd63e39]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2c76e369]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2c76e369]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@69198891]: [Thread[main,5,main]]: checkRunning(false) entered [Server@69198891]: [Thread[main,5,main]]: checkRunning(false) exited [Server@69198891]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@69198891]: [Thread[main,5,main]]: checkRunning(false) entered [Server@69198891]: [Thread[main,5,main]]: checkRunning(false) exited [Server@69198891]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@a761fe]: [Thread[main,5,main]]: checkRunning(false) entered [Server@a761fe]: [Thread[main,5,main]]: checkRunning(false) exited [Server@a761fe]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@a761fe]: [Thread[main,5,main]]: checkRunning(false) entered [Server@a761fe]: [Thread[main,5,main]]: checkRunning(false) exited [Server@a761fe]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.422 sec Running ch.qos.logback.access.jetty.JettyBasicTest 2007-01-19 10:02:21.031::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2007-01-19 10:02:21.188::INFO: jetty-6.1.1 2007-01-19 10:02:21.339::INFO: Started SelectChannelConnector @ 0.0.0.0:1234 19/01/2007:10:02:21 +0100 localhost 127.0.0.1 19/01/2007:10:02:21 +0100 localhost 127.0.0.1 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.482 sec <<< FAILURE! Running ch.qos.logback.access.filter.AccessStatsTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running ch.qos.logback.access.pattern.ConverterTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec Running ch.qos.logback.access.filter.StatsByDayTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running ch.qos.logback.access.net.URLEvaluatorTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec Running ch.qos.logback.access.net.SocketAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.19 sec Results : Tests run: 29, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 13 seconds [INFO] Finished at: Fri Jan 19 10:02:22 CET 2007 [INFO] Final Memory: 16M/118M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

[continuum] BUILD FAILURE: Logback Access Module
by John Noreplai 19 Jan '07

19 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Failed Started at: Fri, 19 Jan 2007 10:01:14 +0100 Finished at: Fri, 19 Jan 2007 10:01:48 +0100 Total time: 34s Build Trigger: Forced Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Access Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/jetty/6.1.1/jetty-6.1.1.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/project/6.1.1/project-6.1.1… 11K downloaded Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-util/6.1.1/jetty-util… 2K downloaded Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/servlet-api-2.5/6.1.1/servl… 2K downloaded Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/servlet-api-2.5/6.1.1/servl… 128K downloaded Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-util/6.1.1/jetty-util… 113K downloaded Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/jetty/6.1.1/jetty-6.1.1.jar 449K downloaded [INFO] [compiler:compile] Compiling 64 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] [retrotranslator:translate {execution: default}] [INFO] Transforming 80 file(s) from /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/logback-access-0.8.1-SNAPSHOT-jdk14.jar. [INFO] Transformation of 80 file(s) completed successfully. [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.access.db.DBAppenderTest [Server@2d92b996]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2d92b996]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2d92b996]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@2d92b996]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2d92b996]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2d92b996]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@314c194d]: [Thread[main,5,main]]: checkRunning(false) entered [Server@314c194d]: [Thread[main,5,main]]: checkRunning(false) exited [Server@314c194d]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@314c194d]: [Thread[main,5,main]]: checkRunning(false) entered [Server@314c194d]: [Thread[main,5,main]]: checkRunning(false) exited [Server@314c194d]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@37bd2664]: [Thread[main,5,main]]: checkRunning(false) entered [Server@37bd2664]: [Thread[main,5,main]]: checkRunning(false) exited [Server@37bd2664]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@37bd2664]: [Thread[main,5,main]]: checkRunning(false) entered [Server@37bd2664]: [Thread[main,5,main]]: checkRunning(false) exited [Server@37bd2664]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@5430d082]: [Thread[main,5,main]]: checkRunning(false) entered [Server@5430d082]: [Thread[main,5,main]]: checkRunning(false) exited [Server@5430d082]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@5430d082]: [Thread[main,5,main]]: checkRunning(false) entered [Server@5430d082]: [Thread[main,5,main]]: checkRunning(false) exited [Server@5430d082]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.757 sec <<< FAILURE! Running ch.qos.logback.access.jetty.JettyBasicTest 2007-01-19 10:01:47.114::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2007-01-19 10:01:47.175::INFO: jetty-6.1.1 2007-01-19 10:01:47.263::INFO: Started SelectChannelConnector @ 0.0.0.0:1234 19/01/2007:10:01:47 +0100 localhost 127.0.0.1 19/01/2007:10:01:47 +0100 localhost 127.0.0.1 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.302 sec Running ch.qos.logback.access.filter.AccessStatsTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running ch.qos.logback.access.pattern.ConverterTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec Running ch.qos.logback.access.filter.StatsByDayTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running ch.qos.logback.access.net.URLEvaluatorTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running ch.qos.logback.access.net.SocketAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.128 sec Results : Tests run: 29, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 32 seconds [INFO] Finished at: Fri Jan 19 10:01:48 CET 2007 [INFO] Final Memory: 17M/144M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

[continuum] BUILD FAILURE: Logback Access Module
by John Noreplai 19 Jan '07

19 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Failed Started at: Fri, 19 Jan 2007 09:57:54 +0100 Finished at: Fri, 19 Jan 2007 09:58:07 +0100 Total time: 13s Build Trigger: Forced Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Access Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 64 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /opt/continuum-1.0.3/apps/continuum/working-directory/47/src/main/java/ch/qos/logback/access/jetty/JettyServerAdapter.java:[41,36] cannot find symbol symbol : method getHttpFields() location: class org.mortbay.jetty.Response [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10 seconds [INFO] Finished at: Fri Jan 19 09:58:07 CET 2007 [INFO] Final Memory: 13M/118M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

svn commit: r1255 - logback/trunk
by noreply.seb＠qos.ch 19 Jan '07

19 Jan '07

Author: seb Date: Fri Jan 19 09:44:35 2007 New Revision: 1255 Modified: logback/trunk/pom.xml Log: updated jetty's version number Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Fri Jan 19 09:44:35 2007 @@ -103,12 +103,12 @@ <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty</artifactId> - <version>6.0.0</version> + <version>6.1.1</version> </dependency> <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>servlet-api-2.5</artifactId> - <version>6.0.0</version> + <version>6.1.1</version> </dependency> <dependency> <groupId>javax.jms</groupId>

1 0

[continuum] BUILD FAILURE: Logback Access Module
by John Noreplai 18 Jan '07

18 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Ok Started at: Thu, 18 Jan 2007 17:20:40 +0100 Finished at: Thu, 18 Jan 2007 17:20:47 +0100 Total time: 7s Build Trigger: Schedule Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes ceki Added support for the http response, including contents. /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/Constants.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/PatternLayout.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/jetty/JettyServerAdapter.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/FullResponseConverter.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/ResponseContentConverter.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeFilter.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeHttpServletResponse.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeServletOutputStream.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/spi/AccessEvent.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/spi/ServerAdapter.java /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/tomcat/TomcatServerAdapter.java /logback/trunk/logback-access/src/test/java/ch/qos/logback/access/pattern/helpers/DummyServerAdapter.java /logback/trunk/logback-access/src/test/java/ch/qos/logback/access/pattern/helpers/DummyValuesAdapter.java ceki will fix later /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/FullResponseConverter.java ceki writer can be null /logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeHttpServletResponse.java **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Access Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 64 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /opt/continuum-1.0.3/apps/continuum/working-directory/47/src/main/java/ch/qos/logback/access/jetty/JettyServerAdapter.java:[41,36] cannot find symbol symbol : method getHttpFields() location: class org.mortbay.jetty.Response [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5 seconds [INFO] Finished at: Thu Jan 18 17:20:46 CET 2007 [INFO] Final Memory: 14M/143M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

svn commit: r1254 - logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet
by noreply.ceki＠qos.ch 18 Jan '07

18 Jan '07

Author: ceki Date: Thu Jan 18 17:09:33 2007 New Revision: 1254 Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeHttpServletResponse.java Log: writer can be null Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeHttpServletResponse.java ============================================================================== --- logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeHttpServletResponse.java (original) +++ logback/trunk/logback-access/src/main/java/ch/qos/logback/access/servlet/TeeHttpServletResponse.java Thu Jan 18 17:09:33 2007 @@ -49,7 +49,11 @@ void finish() throws IOException { - this.writer.close(); - teeServletOutputStream.close(); + if(this.writer != null) { + this.writer.close(); + } + if(this.teeServletOutputStream != null) { + this.teeServletOutputStream.close(); + } } }

1 0

svn commit: r1253 - in logback/trunk: logback-classic/src/main/java/ch/qos/logback/classic logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 18 Jan '07

18 Jan '07

Author: seb Date: Thu Jan 18 17:06:56 2007 New Revision: 1253 Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml Log: documented new marker converter Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java Thu Jan 18 17:06:56 2007 @@ -42,7 +42,7 @@ * conversion pattern. * * For more information about this layout, please refer to the online manual at - * http://logback.qos.ch/manual/layouts.html#ClassicPatternLayout + * http://logback.qos.ch/manual/layouts.html#PatternLayout * */ Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml Thu Jan 18 17:06:56 2007 @@ -283,7 +283,7 @@ - <a name="ClassicPatternLayout" /> + <a name="PatternLayout" /> <h3>PatternLayout</h3> @@ -789,7 +789,26 @@ </td> </tr> - + + <tr> + <td align="center"> + marker + </td> + + <td> + + Used to output the marker associated with the logger request. + + + If there is a single marker available, its name is displayed. + In case the marker has children markers, the converter displays + the parent's and children's names as shown below. + + + parentName [ child1, child2 ] + + </td> + </tr> <tr> <td align="center">

1 0

svn commit: r1252 - logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern
by noreply.ceki＠qos.ch 18 Jan '07

18 Jan '07

Author: ceki Date: Thu Jan 18 17:06:40 2007 New Revision: 1252 Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/FullResponseConverter.java Log: will fix later Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/FullResponseConverter.java ============================================================================== --- logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/FullResponseConverter.java (original) +++ logback/trunk/logback-access/src/main/java/ch/qos/logback/access/pattern/FullResponseConverter.java Thu Jan 18 17:06:40 2007 @@ -13,7 +13,7 @@ buf.append("HTTP/1.1 "); buf.append(ae.getStatusCode()); - buf.append(" NA"); + buf.append(" DO_FIXME"); buf.append(Layout.LINE_SEP); List<String> hnList = ae.getResponseHeaderNameList();

1 0