- logback-dev - mailman3.qos.ch

svn commit: r1590 - in logback/trunk: logback-core/src/main/java/ch/qos/logback/core logback-examples/src/main/java/chapter4 logback-examples/src/main/java/chapter4/conf logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 12 Sep '07

12 Sep '07

Author: ceki Date: Wed Sep 12 23:20:15 2007 New Revision: 1590 Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/ConsoleAppender.java logback/trunk/logback-examples/src/main/java/chapter4/ConfigurationTester.java logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-fileAppender.xml logback/trunk/logback-site/src/site/pages/manual/appenders.html Log: - minor changes - better docs in appenders.html Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/ConsoleAppender.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/ConsoleAppender.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/ConsoleAppender.java Wed Sep 12 23:20:15 2007 @@ -1,11 +1,11 @@ /** - * LOGBack: the reliable, fast and flexible logging library for Java. - * - * Copyright (C) 1999-2006, QOS.ch - * - * This library is free software, you can redistribute it and/or - * modify it under the terms of the GNU Lesser General Public License as - * published by the Free Software Foundation. + * Logback: the generic, reliable, fast and flexible logging framework. + * + * Copyright (C) 1999-2007, QOS.ch + * + * This library is free software, you can redistribute it and/or modify it under + * the terms of the GNU Lesser General Public License as published by the Free + * Software Foundation. */ package ch.qos.logback.core; @@ -31,7 +31,7 @@ protected String target = SYSTEM_OUT; /** - * As in most cases, the default constructor does nothing. + * As in most logback components, the default constructor does nothing. */ public ConsoleAppender() { } Modified: logback/trunk/logback-examples/src/main/java/chapter4/ConfigurationTester.java ============================================================================== --- logback/trunk/logback-examples/src/main/java/chapter4/ConfigurationTester.java (original) +++ logback/trunk/logback-examples/src/main/java/chapter4/ConfigurationTester.java Wed Sep 12 23:20:15 2007 @@ -1,3 +1,12 @@ +/** + * Logback: the generic, reliable, fast and flexible logging framework. + * + * Copyright (C) 1999-2007, QOS.ch + * + * This library is free software, you can redistribute it and/or modify it under + * the terms of the GNU Lesser General Public License as published by the Free + * Software Foundation. + */ package chapter4; import org.slf4j.Logger; @@ -37,6 +46,10 @@ } catch (JoranException je) { je.printStackTrace(); } + // After we've called Joran, let's print information about the + // internal status of logback + StatusPrinter.print(lc.getStatusManager()); + logger.debug("**Hello {}", new Bar()); MDC.put("testKey", "testValueFromMDC"); MDC.put("testKey2", "value2"); @@ -45,7 +58,5 @@ } Bar bar = new Bar(); bar.createLoggingRequest(); - - StatusPrinter.print(lc.getStatusManager()); } } Modified: logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-fileAppender.xml ============================================================================== --- logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-fileAppender.xml (original) +++ logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-fileAppender.xml Wed Sep 12 23:20:15 2007 @@ -3,9 +3,6 @@ <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <File>testFile.log</File> <Append>true</Append> - <Encoding>UTF-8</Encoding> - <BufferedIO>false</BufferedIO> - <ImmediateFlush>true</ImmediateFlush> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</Pattern> Modified: logback/trunk/logback-site/src/site/pages/manual/appenders.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/appenders.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/appenders.html Wed Sep 12 23:20:15 2007 @@ -286,10 +286,9 @@ </tr> </table> - - In general, if you disable immediate flushing, then make sure to flush - any output streams when your application exits. Otherwise, log messages - will be lost as illustrated by the next example. + In general, if you disable immediate flushing, then make sure to + flush any output streams when your application exits. Otherwise, log + messages will be lost as illustrated by the next example. Example 4.1: Exiting an application without flushing (<a href="../xref/chapter4/ExitWoes1.html">logback-examples/src/main/java/chapter4/ExitWoes1.java</a>) @@ -325,31 +324,29 @@ } }</pre></div> - - This example creates a <code>WriterAppender</code> that uses an - <code>OutputStreamWriter</code> - wrapping a <code>FileOutputStream</code> as its underlying <code>Writer</code> object, - with immediate flushing disabled. It then proceeds to log a single debug message. - According to <code>OutputStreamWriter</code> javadocs, each invocation of a - <code>write()</code> - method causes the encoding converter to be invoked on the given character(s). - The resulting bytes are accumulated in a buffer before being written - to the underlying output stream. As astonishing as this may seem, - running <code>ExitWoes1</code> will not produce any output in the file - exitWoes1.log - because the Java VM does not flush output streams when it exits. - Calling the <code>shutdownAndReset()</code> method of a <code>LoggerContext</code> - ensures that all - appenders in the hierarchy are closed and their buffers are flushed. The - <code>ExitWoes2</code> class uses this statement and outputs a logging - request. + This example creates a <code>WriterAppender</code> that uses an + <code>OutputStreamWriter</code> wrapping a + <code>FileOutputStream</code> as its underlying <code>Writer</code> + object, with immediate flushing disabled. It then proceeds to log a + single debug message. According to <code>OutputStreamWriter</code> + javadocs, each invocation of a <code>write()</code> method causes + the encoding converter to be invoked on the given character(s). The + resulting bytes are accumulated in a buffer before being written to + the underlying output stream. As astonishing as this may seem, + running <code>ExitWoes1</code> will not produce any data in the file + exitWoes1.log because the Java VM does not flush output + streams when it exits. Calling the <code>shutdownAndReset()</code> + method of a <code>LoggerContext</code> ensures that all appenders in + the hierarchy are closed and their buffers are flushed. The <code><a + href="../xref/chapter4/ExitWoes2.html">ExitWoes2</a></code> class + uses this statement and outputs a logging request. - - The <code>WriterAppender</code> is the super class of four other appenders, - namely <code>ConsoleAppender</code>, <code>FileAppender</code> which in turn is - the super class of <code>RollingFileAppender</code>. The next figure illustrates - the class diagram for <code>WriterAppender</code> and its subclasses. + The <code>WriterAppender</code> is the super class of three other + appenders, namely <code>ConsoleAppender</code>, + <code>FileAppender</code> which in turn is the super class of + <code>RollingFileAppender</code>. The next figure illustrates the + class diagram for <code>WriterAppender</code> and its subclasses. <img src="images/chapter4/fileAppenderUML.png" alt="A UML diagram showing FileAppender"/> @@ -357,15 +354,16 @@ <a name="ConsoleAppender"></a> <h3>ConsoleAppender</h3> - - The <a href="../xref/ch/qos/logback/core/ConsoleAppender.html"> - <code>ConsoleAppender</code></a>, as the name indicates, appends on the console, - or more precisely on System.out or System.err, the former - being the default target. <code>ConsoleAppender</code> formats events with - a layout specified by the user. Both System.out and System.err - are <code>java.io.PrintStream</code> objects. - Consequently, they are wrapped inside an <code>OutputStreamWriter</code> - which buffers I/O operations but not character conversions. + The <a href="../xref/ch/qos/logback/core/ConsoleAppender.html"> + <code>ConsoleAppender</code></a>, as the name indicates, appends on + the console, or more precisely on System.out or + System.err, the former being the default + target. <code>ConsoleAppender</code> formats events with a layout + specified by the user. Layouts will be discussed in the next + chapter. Both System.out and System.err are + <code>java.io.PrintStream</code> objects. Consequently, they are + wrapped inside an <code>OutputStreamWriter</code> which buffers I/O + operations but not character conversions. <table class="bodyTable"> @@ -394,8 +392,8 @@ </tr> </table> - - Here is a sample configuration that uses <code>ConsoleAppender</code>. + Here is a sample configuration that uses + <code>ConsoleAppender</code>. Example 4.2: ConsoleAppender configuration (logback-examples/src/main/java/chapter4/conf/logback-Console.xml) @@ -414,29 +412,32 @@ </root> </configuration></pre></div> - - To run this example, just issue the following command, - once in the logback-examples directory: + After you have set your current path to the + logback-examples directory, you can give the above + configuration file a whirl by issuing the following command: - -<div class="source"><pre>java chapter4.ConfigurationTester src/main/java/chapter4/conf/logback-Console.xml</pre></div> + +<div class="source"><pre>java <a +href="../xref/chapter4/ConfigurationTester.html">chapter4.ConfigurationTester</a> src/main/java/chapter4/conf/logback-Console.xml</pre></div> <a name="FileAppender"></a> <h3>FileAppender</h3> - - The <a href="../xref/ch/qos/logback/core/FileAppender.html"><code>FileAppender</code></a>, - a subclass of <code>WriterAppender</code>, - appends log events into a file. The file to write to is specified by - the File option. - If the file already exists, it is either appended to, or truncated - depending on the value of the Append option. - It uses a <code>FileOutputStream</code> which is wrapped by an <code>OutputStreamWriter</code>. - Note that <code>OutputStreamWriter</code> buffers I/O operations - but not character conversions. To optimize character conversions one - can set the BufferedIO option to true - which effectively wraps the <code>OutputStreamWriter</code> with - a <code>BufferedWriter</code>. Options for <code>FileAppender</code> are summarized below. + The <a + href="../xref/ch/qos/logback/core/FileAppender.html"><code>FileAppender</code></a>, + a subclass of <code>WriterAppender</code>, appends log events into a + file. The target fileis specified by the File option. If the file already exists, it + is either appended to, or truncated depending on the value of the + Append option. + <code>FileAppender</code> uses a <code>FileOutputStream</code> which + is wrapped by an <code>OutputStreamWriter</code>. Note that + <code>OutputStreamWriter</code> buffers I/O operations but not + character conversions. To optimize character conversions one can set + the BufferedIO option to true which + effectively wraps the <code>OutputStreamWriter</code> with a + <code>BufferedWriter</code>. Options for <code>FileAppender</code> + are summarized below. <table class="bodyTable"> @@ -448,9 +449,11 @@ <tr class="b"> <td>Append</td> <td><code>boolean</code></td> - <td>If true, events are appended at the end of an existing file. - Otherwise, if Append is false, any existing - file is truncated. The Append option is set to true by default.</td> + <td>If true, events are appended at the end of an existing file. + Otherwise, if Append is false, any + existing file is truncated. The Append option is set to true by + default.</td> </tr> <tr class="a"> <td>Encoding</td> @@ -460,17 +463,18 @@ <tr class="b"> <td>BufferedIO</td> <td><code>boolean</code></td> - <td> - The BufferedIO option is set to false by default. - If set to true, the underlying <code>OutputStreamWriter</code> is wrapped - by a <code>BufferedWriter</code> object. - Setting BufferedIO to true automatically - sets the ImmediateFlush option to false. - The name BufferedIO is slightly misleading because - buffered IO is already supported by <code>OutputStreamWriter</code>. - Setting BufferedIO to true has the effect of - buffering I/O as well as character to raw byte conversions, saving a few - CPU cycles in the process. + <td>The BufferedIO option is set to + false by default. If set to true, the underlying + <code>OutputStreamWriter</code> is wrapped by a + <code>BufferedWriter</code> object. Setting BufferedIO to true automatically sets the + ImmediateFlush option to false. The + name BufferedIO is slightly + misleading because buffered IO is already supported by + <code>OutputStreamWriter</code>. Setting BufferedIO to true has the effect of + buffering I/O as well as character to raw byte conversions, + saving a few CPU cycles in the process. </td> </tr> <tr class="a"> @@ -481,48 +485,48 @@ <tr class="b"> <td>File</td> <td><code>String</code></td> - <td> - The name of the file to write to. If the file does not exist, it is created. - On the MS Windows platform users frequently forget to escape back slashes. - For example, the value c:\temp\test.log is not likely to be interpreted - properly as '\t' is an escape sequence interpreted as a single - tab character (\u0009). - Correct values can be specified as c:/temp/test.log or - alternatively as c:\\temp\\test.log. - The File option has no default value. + <td>The name of the file to write to. If the file does not + exist, it is created. On the MS Windows platform users + frequently forget to escape back slashes. For example, the + value c:\temp\test.log is not likely to be interpreted + properly as '\t' is an escape sequence interpreted as a + single tab character (\u0009). Correct values can be + specified as c:/temp/test.log or alternatively as + c:\\temp\\test.log. The File option has no default value. </td> </tr> <tr class="a"> <td>ImmediateFlush</td> <td><code>boolean</code></td> - <td> - See <code>WriterAppender</code> options. - </td> + <td>See <code>WriterAppender</code> options.</td> </tr> </table> - - By default, <code>FileAppender</code> performs a flush operation for - each event, ensuring that events are immediately written to disk. - Setting the ImmediateFlush option to false can drastically reduce - I/O activity by letting <code>OutputStreamWriter</code> buffer bytes - before writing them on disk. For short messages, we have observed 2 or 3 - fold increases in logging throughput, i.e. the number of logs output - per unit of time. For longer messages, the throughput gains are somewhat - less dramatic, and range between 1.4 and 2 fold. Enabling the - BufferedIO - option, that is buffering character to byte conversions, increases - performance by an additional 10% to 40% compared to only disk - I/O buffering (ImmediateFlush=false). - Performance varies somewhat depending on the host machine as well as JDK version. - Throughput measurements are based on the <code>chapter4.IO</code> application. - Please refer to <a href="../xref/chapter4/IO.html"> - logback-examples/src/main/java/chapter4/IO.java</a> - for actual source code. + By default, <code>FileAppender</code> performs a flushes each + event, ensuring that events are immediately written to disk. + Setting the ImmediateFlush option to + false can drastically reduce I/O activity by letting + <code>OutputStreamWriter</code> buffer bytes before writing them on + disk. For short messages, we have observed 2 or 3 fold increases in + logging throughput, i.e. the number of logs output per unit of + time. For longer messages, the throughput gains are somewhat less + dramatic, and range between 1.4 and 2 fold. Enabling the BufferedIO option, that is buffering character + to byte conversions, increases performance by an additional 10% to + 40% compared to only disk I/O buffering (ImmediateFlush=false). Performance varies + somewhat depending on the host machine as well as JDK version. + Throughput measurements are based on the <code>chapter4.IO</code> + application. Please refer to <a href="../xref/chapter4/IO.html"> + logback-examples/src/main/java/chapter4/IO.java</a> for + actual source code. - - Configuring <code>FileAppender</code> can be done the following way: +  + + Configuring <code>FileAppender</code> can be done the following + way: Example 4.3: FileAppender configuration (logback-examples/src/main/java/chapter4/conf/logback-fileAppender.xml) @@ -531,9 +535,6 @@ <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <File>testFile.log</File> <Append>true</Append> - <Encoding>UTF-8</Encoding> - <BufferedIO>false</BufferedIO> - <ImmediateFlush>true</ImmediateFlush> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</Pattern>

1 0

[continuum] BUILD SUCCESSFUL: Logback Examples Module
by John Noreplai 12 Sep '07

12 Sep '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Ok Previous State: Failed Started at: Wed, 12 Sep 2007 23:14:11 +0200 Finished at: Wed, 12 Sep 2007 23:14:19 +0200 Total time: 8s Build Trigger: Forced Exit code: 0 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 Examples Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/50/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 49 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [jar:jar] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/logback-examples-0.9.9-SNAPSHOT.jar [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [INFO] [source:jar {execution: default}] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/logback-examples-0.9.9-SNAPSHOT-sources.jar [INFO] [install:install] [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/logback-examples-0.9.9-SNAPSHOT.jar to /root/.m2/repository/ch/qos/logback/logback-examples/0.9.9-SNAPSHOT/logback-examples-0.9.9-SNAPSHOT.jar [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/logback-examples-0.9.9-SNAPSHOT-sources.jar to /root/.m2/repository/ch/qos/logback/logback-examples/0.9.9-SNAPSHOT/logback-examples-0.9.9-SNAPSHOT-sources.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6 seconds [INFO] Finished at: Wed Sep 12 23:14:18 CEST 2007 [INFO] Final Memory: 15M/118M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

[continuum] BUILD SUCCESSFUL: Logback Classic Module
by John Noreplai 12 Sep '07

12 Sep '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Ok Previous State: Failed Started at: Wed, 12 Sep 2007 23:13:50 +0200 Finished at: Wed, 12 Sep 2007 23:14:09 +0200 Total time: 19s Build Trigger: Forced Exit code: 0 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 Classic Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 90 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 90 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.classic.LoggerContextTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.075 sec Running ch.qos.logback.classic.pattern.ClassNameAbbreviatorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running ch.qos.logback.classic.TurboFilteringInLoggerTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec Running ch.qos.logback.classic.pattern.MDCConverterTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec Running ch.qos.logback.classic.util.TestConstants Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running ch.qos.logback.classic.PatternLayoutTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec Running ch.qos.logback.classic.MessageFormattingTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running ch.qos.logback.classic.pattern.ConverterTest Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec Running ch.qos.logback.classic.selector.ContextJNDISelectorTest MockInitialContextFactory static called Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.051 sec Running ch.qos.logback.classic.DynamicLoggerContextTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.725 sec Running ch.qos.logback.classic.control.TestAction Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running ch.qos.logback.classic.util.InitializationTest TEST 23:14:05.011 [main] DEBUG c.q.l.c.util.InitializationTest - Hello-didily-odily TEST 23:14:05.012 [main] DEBUG c.q.l.c.util.InitializationTest - Hello-didily-odily Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.db.DBAppenderTest [Server@5ef4f44a]: [Thread[main,5,main]]: checkRunning(false) entered [Server@5ef4f44a]: [Thread[main,5,main]]: checkRunning(false) exited [Server@5ef4f44a]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@5ef4f44a]: [Thread[main,5,main]]: checkRunning(false) entered [Server@5ef4f44a]: [Thread[main,5,main]]: checkRunning(false) exited [Server@5ef4f44a]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@5ef4f44a]: [Thread[main,5,main]]: setTrace(false) [Server@5ef4f44a]: [Thread[main,5,main]]: setSilent(false) [Server@5ef4f44a]: [Thread[main,5,main]]: start() entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: run() entered [Server@5ef4f44a]: Initiating startup sequence... [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.tls=false [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.port=9001 [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.trace=false [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.restart_on_shutdown=false [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.no_system_exit=true [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.silent=false [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.default_page=index.html [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.address=0.0.0.0 [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.dbname.0=test [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: server.root=. [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: openServerSocket() entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@5ef4f44a]: Server socket opened successfully in 4 ms. [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: openServerSocket() exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: openDatabases() entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@5ef4f44a]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 195 ms. [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: openDatabases() exiting [Server@5ef4f44a]: Startup sequence completed in 201 ms. [Server@5ef4f44a]: 2007-09-12 23:14:05.301 HSQLDB server 1.8.0 is online [Server@5ef4f44a]: To close normally, connect and execute SHUTDOWN SQL [Server@5ef4f44a]: From command line, use [Ctrl]+[C] to abort abruptly [Server@5ef4f44a]: [Thread[main,5,main]]: start() exiting 1 [Server@5ef4f44a]: [Thread[main,5,main]]: stop() entered [Server@5ef4f44a]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@5ef4f44a]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@5ef4f44a]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@5ef4f44a]: [Thread[main,5,main]]: stop() exiting [Server@10ad8659]: [Thread[main,5,main]]: checkRunning(false) entered [Server@10ad8659]: [Thread[main,5,main]]: checkRunning(false) exited [Server@10ad8659]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@10ad8659]: [Thread[main,5,main]]: checkRunning(false) entered [Server@10ad8659]: [Thread[main,5,main]]: checkRunning(false) exited [Server@10ad8659]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@10ad8659]: [Thread[main,5,main]]: setTrace(false) [Server@10ad8659]: [Thread[main,5,main]]: setSilent(false) [Server@10ad8659]: [Thread[main,5,main]]: start() entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: shutdown() entered [Server@5ef4f44a]: Initiating shutdown sequence... [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseServerSocket() entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseServerSocket() exited [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) entered [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: releaseDatabase(0) exiting [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: HSQLDB Connections @5ef4f44a destroyed [Server@5ef4f44a]: Shutdown sequence completed in 1 ms. [Server@5ef4f44a]: 2007-09-12 23:14:05.458 SHUTDOWN : System.exit() was not called [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: shutdown() exited [Server@5ef4f44a]: [Thread[HSQLDB Server @5ef4f44a,5,main]]: ServerThread.run() exited [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: run() entered [Server@10ad8659]: Initiating startup sequence... [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.tls=false [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.port=9001 [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.trace=false [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.restart_on_shutdown=false [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.no_system_exit=true [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.silent=false [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.default_page=index.html [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.address=0.0.0.0 [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.dbname.0=test [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: server.root=. [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: openServerSocket() entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@10ad8659]: Server socket opened successfully in 0 ms. [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: openServerSocket() exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: openDatabases() entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@10ad8659]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 0 ms. [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: openDatabases() exiting [Server@10ad8659]: Startup sequence completed in 1 ms. [Server@10ad8659]: 2007-09-12 23:14:05.460 HSQLDB server 1.8.0 is online [Server@10ad8659]: To close normally, connect and execute SHUTDOWN SQL [Server@10ad8659]: From command line, use [Ctrl]+[C] to abort abruptly [Server@10ad8659]: [Thread[main,5,main]]: start() exiting 1 [Server@10ad8659]: [Thread[main,5,main]]: stop() entered [Server@10ad8659]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@10ad8659]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@10ad8659]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@10ad8659]: [Thread[main,5,main]]: stop() exiting [Server@704f459c]: [Thread[main,5,main]]: checkRunning(false) entered [Server@704f459c]: [Thread[main,5,main]]: checkRunning(false) exited [Server@704f459c]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@704f459c]: [Thread[main,5,main]]: checkRunning(false) entered [Server@704f459c]: [Thread[main,5,main]]: checkRunning(false) exited [Server@704f459c]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@704f459c]: [Thread[main,5,main]]: setTrace(false) [Server@704f459c]: [Thread[main,5,main]]: setSilent(false) [Server@704f459c]: [Thread[main,5,main]]: start() entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: shutdown() entered [Server@10ad8659]: Initiating shutdown sequence... [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseServerSocket() entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseServerSocket() exited [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) entered [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: releaseDatabase(0) exiting [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: HSQLDB Connections @10ad8659 destroyed [Server@10ad8659]: Shutdown sequence completed in 1 ms. [Server@10ad8659]: 2007-09-12 23:14:05.571 SHUTDOWN : System.exit() was not called [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: shutdown() exited [Server@10ad8659]: [Thread[HSQLDB Server @10ad8659,5,main]]: ServerThread.run() exited [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: run() entered [Server@704f459c]: Initiating startup sequence... [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.tls=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.port=9001 [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.trace=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.restart_on_shutdown=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.no_system_exit=true [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.silent=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.default_page=index.html [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.address=0.0.0.0 [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.dbname.0=test [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: server.root=. [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: openServerSocket() entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@704f459c]: Server socket opened successfully in 0 ms. [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: openServerSocket() exiting [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: openDatabases() entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@704f459c]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 0 ms. [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: openDatabases() exiting [Server@704f459c]: Startup sequence completed in 1 ms. [Server@704f459c]: 2007-09-12 23:14:05.573 HSQLDB server 1.8.0 is online [Server@704f459c]: To close normally, connect and execute SHUTDOWN SQL [Server@704f459c]: From command line, use [Ctrl]+[C] to abort abruptly [Server@704f459c]: [Thread[main,5,main]]: start() exiting 1 [Server@704f459c]: [Thread[main,5,main]]: stop() entered [Server@704f459c]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@704f459c]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@704f459c]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@704f459c]: [Thread[main,5,main]]: stop() exiting [Server@64633e5e]: [Thread[main,5,main]]: checkRunning(false) entered [Server@64633e5e]: [Thread[main,5,main]]: checkRunning(false) exited [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: shutdown() entered [Server@64633e5e]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@704f459c]: Initiating shutdown sequence... [Server@64633e5e]: [Thread[main,5,main]]: checkRunning(false) entered [Server@64633e5e]: [Thread[main,5,main]]: checkRunning(false) exited [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseServerSocket() entered [Server@64633e5e]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseServerSocket() exited [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[main,5,main]]: setTrace(false) [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[main,5,main]]: setSilent(false) [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[main,5,main]]: start() entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: run() entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: Initiating startup sequence... [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.tls=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.port=9001 [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.trace=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.restart_on_shutdown=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.no_system_exit=true [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.silent=false [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.default_page=index.html [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.address=0.0.0.0 [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.dbname.0=test [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: server.root=. [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: openServerSocket() entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: HSQLDB Connections @704f459c destroyed [Server@704f459c]: Shutdown sequence completed in 1 ms. [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@64633e5e]: Server socket opened successfully in 0 ms. [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: openServerSocket() exiting [Server@704f459c]: 2007-09-12 23:14:05.682 SHUTDOWN : System.exit() was not called [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: openDatabases() entered [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: shutdown() exited [Server@704f459c]: [Thread[HSQLDB Server @704f459c,5,main]]: ServerThread.run() exited [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@64633e5e]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 0 ms. [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: openDatabases() exiting [Server@64633e5e]: Startup sequence completed in 0 ms. [Server@64633e5e]: 2007-09-12 23:14:05.682 HSQLDB server 1.8.0 is online [Server@64633e5e]: To close normally, connect and execute SHUTDOWN SQL [Server@64633e5e]: From command line, use [Ctrl]+[C] to abort abruptly [Server@64633e5e]: [Thread[main,5,main]]: start() exiting 1 [Server@64633e5e]: [Thread[main,5,main]]: stop() entered [Server@64633e5e]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@64633e5e]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@64633e5e]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@64633e5e]: [Thread[main,5,main]]: stop() exiting Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.816 sec Running ch.qos.logback.classic.html.HTMLLayoutTest [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: shutdown() entered [Server@64633e5e]: Initiating shutdown sequence... [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseServerSocket() entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseServerSocket() exited [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) entered [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: releaseDatabase(0) exiting [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: HSQLDB Connections @64633e5e destroyed [Server@64633e5e]: Shutdown sequence completed in 1 ms. [Server@64633e5e]: 2007-09-12 23:14:05.838 SHUTDOWN : System.exit() was not called [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: shutdown() exited [Server@64633e5e]: [Thread[HSQLDB Server @64633e5e,5,main]]: ServerThread.run() exited Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.542 sec Running ch.qos.logback.classic.control.RandomUtilTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running ch.qos.logback.classic.turbo.MarkerFilterTest LOGBACK: No context given for ch.qos.logback.classic.turbo.MarkerFilter@2565a3c2 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.net.SocketAppenderTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.588 sec Running ch.qos.logback.classic.control.ScenarioMakerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec Running ch.qos.logback.classic.net.LoggingEventSerializationTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running ch.qos.logback.classic.control.CLCTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.selector.ContextDetachingSCLTest About to detach context named toto No context named toto was found. About to detach context named titi TEST 23:14:07.088 [main] WARN root - Shutting down context titi Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running ch.qos.logback.classic.spi.CallerDataTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.MDCTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running ch.qos.logback.classic.BasicLoggerTest |-WARN in ch.qos.logback.core.read.ListAppender[null] - Attempted to append to non started appender [null]. Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running ch.qos.logback.classic.net.SMTPAppenderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.287 sec Running ch.qos.logback.classic.boolex.JaninoEventEvaluatorTest Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.299 sec Running ch.qos.logback.classic.joran.EvaluatorJoranTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec Running ch.qos.logback.classic.spi.ContextListenerTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running ch.qos.logback.classic.pattern.MarkerConverterTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.net.JMSQueueAppenderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec Running ch.qos.logback.classic.net.JMSTopicAppenderTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running ch.qos.logback.classic.net.SyslogAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.22 sec Running ch.qos.logback.classic.joran.BasicJoranTest |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.read.ListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [LIST] to Logger[root] |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.read.ListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - ch.qos.logback.classic.joran level set to INFO |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [LIST] to Logger[root] |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. |-WARN in ch.qos.logback.classic.joran.action.EvaluatorAction - Assuming default evaluator class [ch.qos.logback.classic.boolex.JaninoEventEvaluator] |-INFO in ch.qos.logback.classic.joran.action.EvaluatorAction - Adding evaluator named [helloEval] to the object stack |-INFO in ch.qos.logback.core.joran.action.MatcherAction - matcher named as [m] |-INFO in ch.qos.logback.core.joran.action.MatcherAction - Popping appender named [m] from the object stack |-INFO in ch.qos.logback.classic.joran.action.EvaluatorAction - Starting evaluator named [helloEval] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.StringListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STR_LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [STR_LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STR_LIST] to Logger[root] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec Results : Tests run: 150, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT.jar [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [INFO] [source:jar {execution: default}] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT-sources.jar [INFO] [jar:jar {execution: bundle-test-jar}] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT.jar [INFO] [jar:test-jar {execution: bundle-test-jar}] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT-tests.jar [INFO] [install:install] [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT.jar to /root/.m2/repository/ch/qos/logback/logback-classic/0.9.9-SNAPSHOT/logback-classic-0.9.9-SNAPSHOT.jar [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT-sources.jar to /root/.m2/repository/ch/qos/logback/logback-classic/0.9.9-SNAPSHOT/logback-classic-0.9.9-SNAPSHOT-sources.jar [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.9-SNAPSHOT-tests.jar to /root/.m2/repository/ch/qos/logback/logback-classic/0.9.9-SNAPSHOT/logback-classic-0.9.9-SNAPSHOT-tests.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 18 seconds [INFO] Finished at: Wed Sep 12 23:14:09 CEST 2007 [INFO] Final Memory: 19M/198M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

[continuum] BUILD FAILURE: Logback Examples Module
by John Noreplai 11 Sep '07

11 Sep '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Ok Started at: Tue, 11 Sep 2007 21:21:10 +0200 Finished at: Tue, 11 Sep 2007 21:21:13 +0200 Total time: 3s 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 - starting work on 0.9.9 - updates to documentation - replaced slf4j-api-1.4.0.jar with slf4j-api-1.4.3.jar /logback/trunk/logback-access/pom.xml /logback/trunk/logback-classic/pom.xml /logback/trunk/logback-core/pom.xml /logback/trunk/logback-examples/lib/slf4j-api-1.4.0.jar /logback/trunk/logback-examples/lib/slf4j-api-1.4.3.jar /logback/trunk/logback-examples/pom.xml /logback/trunk/logback-site/pom.xml /logback/trunk/logback-site/src/site/pages/index.html /logback/trunk/logback-site/src/site/pages/manual/appenders.html /logback/trunk/pom.xml **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Examples Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/50/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/50/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Missing: ---------- 1) ch.qos.logback:logback-classic:jar:0.9.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=ch.qos.logback -DartifactId=logback-classic \ -Dversion=0.9.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) ch.qos.logback:logback-examples:jar:0.9.9-SNAPSHOT 2) ch.qos.logback:logback-classic:jar:0.9.9-SNAPSHOT ---------- 1 required artifact is missing. for artifact: ch.qos.logback:logback-examples:jar:0.9.9-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2 seconds [INFO] Finished at: Tue Sep 11 21:21:13 CEST 2007 [INFO] Final Memory: 11M/83M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

[continuum] BUILD FAILURE: Logback Classic Module
by John Noreplai 11 Sep '07

11 Sep '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Ok Started at: Tue, 11 Sep 2007 21:20:52 +0200 Finished at: Tue, 11 Sep 2007 21:21:09 +0200 Total time: 17s 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 - starting work on 0.9.9 - updates to documentation - replaced slf4j-api-1.4.0.jar with slf4j-api-1.4.3.jar /logback/trunk/logback-access/pom.xml /logback/trunk/logback-classic/pom.xml /logback/trunk/logback-core/pom.xml /logback/trunk/logback-examples/lib/slf4j-api-1.4.0.jar /logback/trunk/logback-examples/lib/slf4j-api-1.4.3.jar /logback/trunk/logback-examples/pom.xml /logback/trunk/logback-site/pom.xml /logback/trunk/logback-site/src/site/pages/index.html /logback/trunk/logback-site/src/site/pages/manual/appenders.html /logback/trunk/pom.xml **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Classic Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 90 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 90 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.classic.LoggerContextTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec Running ch.qos.logback.classic.pattern.ClassNameAbbreviatorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running ch.qos.logback.classic.TurboFilteringInLoggerTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec Running ch.qos.logback.classic.pattern.MDCConverterTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running ch.qos.logback.classic.util.TestConstants Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running ch.qos.logback.classic.PatternLayoutTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec Running ch.qos.logback.classic.MessageFormattingTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running ch.qos.logback.classic.pattern.ConverterTest Tests run: 14, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec <<< FAILURE! Running ch.qos.logback.classic.selector.ContextJNDISelectorTest MockInitialContextFactory static called Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec Running ch.qos.logback.classic.DynamicLoggerContextTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.74 sec Running ch.qos.logback.classic.control.TestAction Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running ch.qos.logback.classic.util.InitializationTest TEST 21:21:05.781 [main] DEBUG c.q.l.c.util.InitializationTest - Hello-didily-odily TEST 21:21:05.782 [main] DEBUG c.q.l.c.util.InitializationTest - Hello-didily-odily Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running ch.qos.logback.classic.db.DBAppenderTest [Server@76497934]: [Thread[main,5,main]]: checkRunning(false) entered [Server@76497934]: [Thread[main,5,main]]: checkRunning(false) exited [Server@76497934]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@76497934]: [Thread[main,5,main]]: checkRunning(false) entered [Server@76497934]: [Thread[main,5,main]]: checkRunning(false) exited [Server@76497934]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@76497934]: [Thread[main,5,main]]: setTrace(false) [Server@76497934]: [Thread[main,5,main]]: setSilent(false) [Server@76497934]: [Thread[main,5,main]]: start() entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: run() entered [Server@76497934]: Initiating startup sequence... [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.tls=false [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.port=9001 [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.trace=false [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.restart_on_shutdown=false [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.no_system_exit=true [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.silent=false [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.default_page=index.html [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.address=0.0.0.0 [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.dbname.0=test [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: server.root=. [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: openServerSocket() entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@76497934]: Server socket opened successfully in 3 ms. [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: openServerSocket() exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: openDatabases() entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@76497934]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 191 ms. [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: openDatabases() exiting [Server@76497934]: Startup sequence completed in 197 ms. [Server@76497934]: 2007-09-11 21:21:06.051 HSQLDB server 1.8.0 is online [Server@76497934]: To close normally, connect and execute SHUTDOWN SQL [Server@76497934]: From command line, use [Ctrl]+[C] to abort abruptly [Server@76497934]: [Thread[main,5,main]]: start() exiting 1 [Server@76497934]: [Thread[main,5,main]]: stop() entered [Server@76497934]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@76497934]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@76497934]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@76497934]: [Thread[main,5,main]]: stop() exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: shutdown() entered [Server@76497934]: Initiating shutdown sequence... [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseServerSocket() entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseServerSocket() exited [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[main,5,main]]: checkRunning(false) entered [Server@30e3c624]: [Thread[main,5,main]]: checkRunning(false) exited [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[main,5,main]]: checkRunning(false) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[main,5,main]]: checkRunning(false) exited [Server@30e3c624]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[main,5,main]]: setTrace(false) [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[main,5,main]]: setSilent(false) [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[main,5,main]]: start() entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) entered [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: run() entered [Server@30e3c624]: Initiating startup sequence... [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: HSQLDB Connections @76497934 destroyed [Server@76497934]: Shutdown sequence completed in 1 ms. [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.tls=false [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.port=9001 [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.trace=false [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.restart_on_shutdown=false [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.no_system_exit=true [Server@76497934]: 2007-09-11 21:21:06.136 SHUTDOWN : System.exit() was not called [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.silent=false [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: shutdown() exited [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.default_page=index.html [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.address=0.0.0.0 [Server@76497934]: [Thread[HSQLDB Server @76497934,5,main]]: ServerThread.run() exited [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.dbname.0=test [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: server.root=. [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: openServerSocket() entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@30e3c624]: Server socket opened successfully in 1 ms. [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: openServerSocket() exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: openDatabases() entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@30e3c624]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 0 ms. [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: openDatabases() exiting [Server@30e3c624]: Startup sequence completed in 6 ms. [Server@30e3c624]: 2007-09-11 21:21:06.142 HSQLDB server 1.8.0 is online [Server@30e3c624]: To close normally, connect and execute SHUTDOWN SQL [Server@30e3c624]: From command line, use [Ctrl]+[C] to abort abruptly [Server@30e3c624]: [Thread[main,5,main]]: start() exiting 1 [Server@30e3c624]: [Thread[main,5,main]]: stop() entered [Server@30e3c624]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@30e3c624]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@30e3c624]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@30e3c624]: [Thread[main,5,main]]: stop() exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: shutdown() entered [Server@30e3c624]: Initiating shutdown sequence... [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseServerSocket() entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseServerSocket() exited [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[main,5,main]]: checkRunning(false) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[main,5,main]]: checkRunning(false) exited [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[main,5,main]]: checkRunning(false) entered [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: HSQLDB Connections @30e3c624 destroyed [Server@39e57e8f]: [Thread[main,5,main]]: checkRunning(false) exited [Server@30e3c624]: Shutdown sequence completed in 1 ms. [Server@39e57e8f]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@30e3c624]: 2007-09-11 21:21:06.248 SHUTDOWN : System.exit() was not called [Server@39e57e8f]: [Thread[main,5,main]]: setTrace(false) [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: shutdown() exited [Server@39e57e8f]: [Thread[main,5,main]]: setSilent(false) [Server@30e3c624]: [Thread[HSQLDB Server @30e3c624,5,main]]: ServerThread.run() exited [Server@39e57e8f]: [Thread[main,5,main]]: start() entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: run() entered [Server@39e57e8f]: Initiating startup sequence... [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.tls=false [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.port=9001 [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.trace=false [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.restart_on_shutdown=false [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.no_system_exit=true [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.silent=false [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.default_page=index.html [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.address=0.0.0.0 [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.dbname.0=test [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: server.root=. [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: openServerSocket() entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@39e57e8f]: Server socket opened successfully in 0 ms. [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: openServerSocket() exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: openDatabases() entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@39e57e8f]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 0 ms. [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: openDatabases() exiting [Server@39e57e8f]: Startup sequence completed in 1 ms. [Server@39e57e8f]: 2007-09-11 21:21:06.250 HSQLDB server 1.8.0 is online [Server@39e57e8f]: To close normally, connect and execute SHUTDOWN SQL [Server@39e57e8f]: From command line, use [Ctrl]+[C] to abort abruptly [Server@39e57e8f]: [Thread[main,5,main]]: start() exiting 1 [Server@39e57e8f]: [Thread[main,5,main]]: stop() entered [Server@39e57e8f]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@39e57e8f]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@39e57e8f]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@39e57e8f]: [Thread[main,5,main]]: stop() exiting [Server@8888e6c]: [Thread[main,5,main]]: checkRunning(false) entered [Server@8888e6c]: [Thread[main,5,main]]: checkRunning(false) exited [Server@8888e6c]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@8888e6c]: [Thread[main,5,main]]: checkRunning(false) entered [Server@8888e6c]: [Thread[main,5,main]]: checkRunning(false) exited [Server@8888e6c]: [Thread[main,5,main]]: setDatabasePath(0,jdbc:hsqldb:mem:test;sql.enforce_strict_size=true) [Server@8888e6c]: [Thread[main,5,main]]: setTrace(false) [Server@8888e6c]: [Thread[main,5,main]]: setSilent(false) [Server@8888e6c]: [Thread[main,5,main]]: start() entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: shutdown() entered [Server@39e57e8f]: Initiating shutdown sequence... [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseServerSocket() entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseServerSocket() exited [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) entered [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: releaseDatabase(0) exiting [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: HSQLDB Connections @39e57e8f destroyed [Server@39e57e8f]: Shutdown sequence completed in 1 ms. [Server@39e57e8f]: 2007-09-11 21:21:06.361 SHUTDOWN : System.exit() was not called [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: shutdown() exited [Server@39e57e8f]: [Thread[HSQLDB Server @39e57e8f,5,main]]: ServerThread.run() exited [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: run() entered [Server@8888e6c]: Initiating startup sequence... [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.tls=false [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.port=9001 [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.trace=false [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.database.0=jdbc:hsqldb:mem:test;sql.enforce_strict_size=true [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.restart_on_shutdown=false [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.no_system_exit=true [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.silent=false [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.default_page=index.html [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.address=0.0.0.0 [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.dbname.0=test [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: server.root=. [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: openServerSocket() entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001] [Server@8888e6c]: Server socket opened successfully in 0 ms. [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: openServerSocket() exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: openDatabases() entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: Opening database: [file:jdbc:hsqldb:mem:test] [Server@8888e6c]: Database [index=0, id=0, db=file:jdbc:hsqldb:mem:test, alias=test] opened sucessfully in 0 ms. [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: openDatabases() exiting [Server@8888e6c]: Startup sequence completed in 0 ms. [Server@8888e6c]: 2007-09-11 21:21:06.362 HSQLDB server 1.8.0 is online [Server@8888e6c]: To close normally, connect and execute SHUTDOWN SQL [Server@8888e6c]: From command line, use [Ctrl]+[C] to abort abruptly [Server@8888e6c]: [Thread[main,5,main]]: start() exiting 1 [Server@8888e6c]: [Thread[main,5,main]]: stop() entered [Server@8888e6c]: [Thread[main,5,main]]: releaseServerSocket() entered [Server@8888e6c]: [Thread[main,5,main]]: Releasing server socket: [ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9001]] [Server@8888e6c]: [Thread[main,5,main]]: releaseServerSocket() exited [Server@8888e6c]: [Thread[main,5,main]]: stop() exiting Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.726 sec Running ch.qos.logback.classic.html.HTMLLayoutTest [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: shutdown() entered [Server@8888e6c]: Initiating shutdown sequence... [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseServerSocket() entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseServerSocket() exited [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) entered [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: releaseDatabase(0) exiting [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: HSQLDB Connections @8888e6c destroyed [Server@8888e6c]: Shutdown sequence completed in 1 ms. [Server@8888e6c]: 2007-09-11 21:21:06.515 SHUTDOWN : System.exit() was not called [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: shutdown() exited [Server@8888e6c]: [Thread[HSQLDB Server @8888e6c,5,main]]: ServerThread.run() exited Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.558 sec Running ch.qos.logback.classic.control.RandomUtilTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec Running ch.qos.logback.classic.turbo.MarkerFilterTest LOGBACK: No context given for ch.qos.logback.classic.turbo.MarkerFilter@f9da4fc Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.net.SocketAppenderTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec Running ch.qos.logback.classic.control.ScenarioMakerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.114 sec Running ch.qos.logback.classic.net.LoggingEventSerializationTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec Running ch.qos.logback.classic.control.CLCTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running ch.qos.logback.classic.selector.ContextDetachingSCLTest About to detach context named toto No context named toto was found. About to detach context named titi TEST 21:21:07.853 [main] WARN root - Shutting down context titi Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running ch.qos.logback.classic.spi.CallerDataTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.MDCTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.212 sec Running ch.qos.logback.classic.BasicLoggerTest |-WARN in ch.qos.logback.core.read.ListAppender[null] - Attempted to append to non started appender [null]. Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running ch.qos.logback.classic.net.SMTPAppenderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.356 sec Running ch.qos.logback.classic.boolex.JaninoEventEvaluatorTest Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.33 sec Running ch.qos.logback.classic.joran.EvaluatorJoranTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec Running ch.qos.logback.classic.spi.ContextListenerTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.pattern.MarkerConverterTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.net.JMSQueueAppenderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec Running ch.qos.logback.classic.net.JMSTopicAppenderTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running ch.qos.logback.classic.net.SyslogAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.223 sec Running ch.qos.logback.classic.joran.BasicJoranTest |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.read.ListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [LIST] to Logger[root] |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.read.ListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - ch.qos.logback.classic.joran level set to INFO |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [LIST] to Logger[root] |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. |-WARN in ch.qos.logback.classic.joran.action.EvaluatorAction - Assuming default evaluator class [ch.qos.logback.classic.boolex.JaninoEventEvaluator] |-INFO in ch.qos.logback.classic.joran.action.EvaluatorAction - Adding evaluator named [helloEval] to the object stack |-INFO in ch.qos.logback.core.joran.action.MatcherAction - matcher named as [m] |-INFO in ch.qos.logback.core.joran.action.MatcherAction - Popping appender named [m] from the object stack |-INFO in ch.qos.logback.classic.joran.action.EvaluatorAction - Starting evaluator named [helloEval] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.StringListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STR_LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [STR_LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STR_LIST] to Logger[root] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec Results : Tests run: 150, Failures: 1, Errors: 0, 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: 15 seconds [INFO] Finished at: Tue Sep 11 21:21:09 CEST 2007 [INFO] Final Memory: 16M/177M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

svn commit: r1589 - in logback/trunk: . logback-access logback-classic logback-core logback-examples logback-examples/lib logback-site logback-site/src/site/pages logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 11 Sep '07

11 Sep '07

Author: ceki Date: Tue Sep 11 21:01:05 2007 New Revision: 1589 Added: logback/trunk/logback-examples/lib/slf4j-api-1.4.3.jar (contents, props changed) Removed: logback/trunk/logback-examples/lib/slf4j-api-1.4.0.jar Modified: logback/trunk/logback-access/pom.xml logback/trunk/logback-classic/pom.xml logback/trunk/logback-core/pom.xml logback/trunk/logback-examples/pom.xml logback/trunk/logback-site/pom.xml logback/trunk/logback-site/src/site/pages/index.html logback/trunk/logback-site/src/site/pages/manual/appenders.html logback/trunk/pom.xml Log: - starting work on 0.9.9 - updates to documentation - replaced slf4j-api-1.4.0.jar with slf4j-api-1.4.3.jar Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Tue Sep 11 21:01:05 2007 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.8</version> + <version>0.9.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Tue Sep 11 21:01:05 2007 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.8</version> + <version>0.9.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Tue Sep 11 21:01:05 2007 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.8</version> + <version>0.9.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Added: logback/trunk/logback-examples/lib/slf4j-api-1.4.3.jar ============================================================================== Binary file. No diff available. Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Tue Sep 11 21:01:05 2007 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.8</version> + <version>0.9.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Tue Sep 11 21:01:05 2007 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.8</version> + <version>0.9.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-site/src/site/pages/index.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/index.html (original) +++ logback/trunk/logback-site/src/site/pages/index.html Tue Sep 11 21:01:05 2007 @@ -44,8 +44,8 @@ The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log - functionality. Note that you can easily build your own modules on - top of the Core module. + functionality. Note that you could easily build your own module + on top of logback-core. Modified: logback/trunk/logback-site/src/site/pages/manual/appenders.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/appenders.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/appenders.html Tue Sep 11 21:01:05 2007 @@ -66,54 +66,52 @@ }</pre></div> - - Most of the methods in the <code>Appender</code> interface are - made of setter and getter methods. A notable exception is the - <code>doAppend()</code> method taking an object instance of type - E as its only parameter. The actual type of E - would vary depending on the logback module. Within the - logback-classic module E would be of type <a - href="../apidocs/ch/qos/logback/classic/spi/LoggingEvent.html">LoggingEvent</a> - and within the logback-access module it would be of type <a - href="../apidocs/ch/qos/logback/access/spi/AccessEvent.html">AccessEvent</a>. - The <code>doAppend()</code> method is perhaps the most important - in the logback framework. It is responsible for outputting the - logging events in a suitable format to the appropriate output - device. Appenders are named entities. This ensures that they can - be referenced by name, a quality confirmed to be especially - significant in configuration scripts. An appender can contain - multiple filters, thus the <code>Appender</code> interface - extending the <code>FilterAttachable</code> interface. Filters - are discussed in detail in a subsequent chapter. - - - - Appenders are ultimately responsible for outputting logging - events. However, they may delegate the actual formatting of the - event to a <code>Layout</code> object. Each layout is associated - with one and only one appender, referred to as the owning - appender. Some appenders have a built-in or fixed event format, - such that they do not require a layout. For example, the - <code>SocketAppender</code> simply serializes logging events - before transmitting them over the wire. + Most of the methods in the <code>Appender</code> interface are + made of setter and getter methods. A notable exception is the + <code>doAppend()</code> method taking an object instance of type + E as its only parameter. The actual type of E + would vary depending on the logback module. Within the + logback-classic module E would be of type <a + href="../apidocs/ch/qos/logback/classic/spi/LoggingEvent.html">LoggingEvent</a> + and within the logback-access module it would be of type <a + href="../apidocs/ch/qos/logback/access/spi/AccessEvent.html">AccessEvent</a>. + The <code>doAppend()</code> method is perhaps the most important in + the logback framework. It is responsible for outputting the logging + events in a suitable format to the appropriate output device. + + + Appenders are named entities. This ensures that they can be + referenced by name, a quality confirmed to be instrumental in + configuration scripts. The <code>Appender</code> interface extends + the <code>FilterAttachable</code> interface. It follows that one or + more filters can be attaqched to an appender instance. Filters are + discussed in detail in a subsequent chapter. + + + Appenders are ultimately responsible for outputting logging + events. However, they may delegate the actual formatting of the + event to a <code>Layout</code> object. Each layout is associated + with one and only one appender, referred to as the owning + appender. Some appenders have a built-in or fixed event + format. Consequently, they do not require nor have a layout. For + example, the <code>SocketAppender</code> simply serializes logging + events before transmitting them over the wire. <a name="AppenderBase"></a> <h2>AppenderBase</h2> - - The <a href="../xref/ch/qos/logback/core/AppenderBase.html"> - <code>ch.qos.logback.core.AppenderBase</code></a> class is an - abstract class implementing the <code>Appender</code> interface. - It provides basic functionality shared by all appenders, such as - methods for getting or setting their name, their activation - status, their layout and their filters. It is the super-class of - all appenders shipped with logback. Although an abstract class, - <code>AppenderBase</code> actually implements the - <code>doAppend()</code> method in the <code>Append</code> - interface. Perhaps the clearest way to discuss - <code>AppenderBase</code> class is by presenting an excerpt of - actual source code. + The <a href="../xref/ch/qos/logback/core/AppenderBase.html"> + <code>ch.qos.logback.core.AppenderBase</code></a> class is an + abstract class implementing the <code>Appender</code> interface. It + provides basic functionality shared by all appenders, such as + methods for getting or setting their name, their activation status, + their layout and their filters. It is the super-class of all + appenders shipped with logback. Although an abstract class, + <code>AppenderBase</code> actually implements the + <code>doAppend()</code> method in the <code>Append</code> interface. + Perhaps the clearest way to discuss <code>AppenderBase</code> class + is by presenting an excerpt of actual source code. <div class="source"><pre>public synchronized void doAppend(E eventObject) { @@ -146,139 +144,143 @@ } }</pre></div> - - This implementation of the <code>doAppend()</code> method is synchronized. - It follows that logging to the same appender from different - threads is safe. While a thread, say T, is executing the <code>doAppend()</code> - method, subsequent calls by other threads are queued until T - leaves the <code>doAppend()</code> method, ensuring - T's exclusive access to the appender. - - - - The first thing the <code>doAppend()</code> method does is to set the - <code>guard</code> variable to <code>true</code>. This ensures that the method will not - call itself and create an infinite loop. Just imagine that a component, called somewhere - beyond the <code>append()</code> - method, wants to log something. Its call could be directed to the very same appender - that just called it, which would then call it again. - - - - The first statement of the <code>doAppend()</code> method, once - the <code>try</code> block is reached, is to check whether the - <code>started</code> field is true. If it is not, - <code>doAppend()</code> will send a warning message and return. - In other words, once stopped, it is impossible to write to a - closed appender. <code>Appender</code> objects implement the - <code>LifeCycle</code> interface, which implies that they - implement <code>start()</code>, <code>stop()</code> and - <code>isStarted()</code> methods. After setting all the options of - an appender, Joran, logback's configuration framework, calls the - <code>start()</code> method to signal the appender to bind or - activate its options. Indeed, depending on the appender, certain - options cannot be activated because of interferences with other - options, or appenders can even not start at all if some options - are missing. For example, since file creation depends on - truncation mode, <code>FileAppender</code> cannot act on the value - of its <code>File</code> option until the value of the Append - option is also known for certain. - - - - If a warning message is sent due to incorrect calls to the - <code>doAppend()</code> method, logback's powerful - <code>Status</code> error reporting system is used. In case - several incorrect calls on <code>doAppend()</code> are issued, - <code>AppenderBase</code> does not send an unlimited number of - warnings. Once a certain limit is reached, the - <code>AppenderBase</code> instance stops its warnings. - - - - The next <code>if</code> statement checks the result of the - attached <code>Filter</code> objects. Depending on the decision - resulting from the filter chain, events can be denied or - alternatively accepted. In the absence of a decision by the - filter chain, events are accepted by default. - - - - Lastly, the <code>doAppend()</code> method invoke the derived - classes' implementation of the <code>append()</code> method, which - does the actual work of appending the event to the appropriate - device. - - - In appenders, the term option or property is reserved for named - attributes that are dynamically inferred using JavaBeans - introspection. - - <h2>Logback Core</h2> - - - Core is logback's central module. It offers functionnalities that - are available to any other module based on logback core. The - <code>Appender</code> classes contained in the core module are can - be used by any module without any customization. - - + This implementation of the <code>doAppend()</code> method is + synchronized. It follows that logging to the same appender from + different threads is safe. While a thread, say T, is + executing the <code>doAppend()</code> method, subsequent calls by + other threads are queued until T leaves the + <code>doAppend()</code> method, ensuring T's exclusive + access to the appender. + + + The first thing the <code>doAppend()</code> method does is to + check whether the guard is set to true. If it is, it immediately + exits. If the guard is not set, it is set to true at the next + statement. The guard ensures that the <code>doAppend()</code> method + will not recursively call itself. Just imagine that a component, + called somewhere beyond the <code>append()</code> method, wants to + log something. Its call could be directed to the very same appender + that just called it. + + + In the following statement we check whether the + <code>started</code> field is true. If it is not, + <code>doAppend()</code> will send a warning message and return. In + other words, once an appender is closed, it is impossible to write + to it. <code>Appender</code> objects implement the + <code>LifeCycle</code> interface, which implies that they implement + <code>start()</code>, <code>stop()</code> and + <code>isStarted()</code> methods. After setting all the options of + an appender, Joran, logback's configuration framework, calls the + <code>start()</code> method to signal the appender to activate its + options. Depending on its kind, an appender may fail to start if + certain options are missing or because of interferences between + various options. For example, given that file creation depends on + truncation mode, <code>FileAppender</code> cannot act on the value + of its <code>File</code> option until the value of the Append option + is also known with certainty. The explicit activation step ensures + that an appender acts on its options after their values + become known. + + + If the appender could not be started or if it has been stopped, a + warning message will be issued through logback's internal status + management system. After several attempts, in order to avoid + flooding the internal status system with copies of the same warning + message, the <code>doAppend()</code> method will stop issuing these + warnings. + + + The next <code>if</code> statement checks the result of the + attached filters. Depending on the decision resulting from the + filter chain, events can be denied or alternatively accepted. In + the absence of a decision by the filter chain, events are accepted + by default. + + + The <code>doAppend()</code> method then invokes the derived + classes' implementation of the <code>append()</code> method. This + method does the actual work of appending the event to the + appropriate device. + + + Finally, the guard is released so as to allow a subsequent + invocation of the <code>doAppend()</code> method. + + + For the remainder of this manual, we reserve the term "option" or + alternatively "property" for any attribute that is inferred + dynamically using JavaBeans introspection through setter and getter + methods. + + <h2>Logback-core</h2> + + Logback-core lays the foundation upon which the other logback + modules are built. In general, the components in logback-core + require some, albeit minimal, amount of customisation. However, in + the next few sections, we describe several appenders which are ready + for use out of the box. + + + <a name="WriterAppender"></a> <h3>WriterAppender</h3> <a - href="../xref/ch/qos/logback/core/WriterAppender.html"><code>WriterAppender</code></a> - appends events to a <code>java.io.Writer</code>. This class - provides basic services that other appenders build upon. Users do - not usually instantiate <code>WriterAppender</code> objects - directly. Since <code>java.io.Writer</code> type cannot be mapped - to a string, there is no way to specify the target - <code>Writer</code> object in a configuration script. Simply put, - you cannot configure a <code>WriterAppender</code> from a script. - However, this does not mean that <code>WriterAppender</code> lacks - configurable options. These options are described next. - - - <table class="bodyTable"> - <tr class="a"> - <th>Option Name</th> - <th>Type</th> - <th>Description</th> - </tr> - <tr class="a"> - <td>Encoding</td> - <td><code>String</code></td> - <td> - The encoding specifies the method of conversion between 16-bit Unicode - characters into raw 8-bit bytes. This appender will use the local platform's - default encoding unless you specify otherwise using the - Encoding option. - According to the <code>java.lang</code> package documentation, acceptable values - are dependent on the VM implementation although all implementations are - required to support at least the following encodings: - US-ASCII, ISO-8859-1, UTF-8, UTF-16BE, - UTF-16LE and UTF-16. - By default, the Encoding option is - <code>null</code> such - that the platform's default encoding is used. + href="../xref/ch/qos/logback/core/WriterAppender.html"><code>WriterAppender</code></a> + appends events to a <code>java.io.Writer</code>. This class + provides basic services that other appenders build upon. Users do + not usually instantiate <code>WriterAppender</code> objects + directly. Since <code>java.io.Writer</code> type cannot be mapped + to a string, as there is no way to specify the target + <code>Writer</code> object in a configuration script. Simply put, + you cannot configure a <code>WriterAppender</code> from a script. + However, this does not mean that <code>WriterAppender</code> lacks + configurable options. These options are described next. + + + <table class="bodyTable"> + <tr class="a"> + <th>Option Name</th> + <th>Type</th> + <th>Description</th> + </tr> + + <tr class="a"> + <td>Encoding</td> + <td><code>String</code></td> + + <td>The encoding specifies the method of conversion between + Java's internal 16-bit Unicode representation of characters into + raw 8-bit bytes. This appender will use the local platform's + default encoding unless you say otherwise by specifying an Encoding value. According to the + <code>java.lang</code> package documentation, acceptable values + are dependent on the VM implementation although all + implementations are required to support at least the following + encodings: US-ASCII, ISO-8859-1, + UTF-8, UTF-16BE, UTF-16LE and + UTF-16. As mentioned previously, by default, the Encoding option is <code>null</code> such + that the platform's default encoding is used. </td> </tr> <tr class="b"> <td>ImmediateFlush</td> <td><code>boolean</code></td> - <td> - If set to true, each write of a logging event is followed by a - flush operation on the underlying <code>Writer</code> - object. Conversely, if the option is set to false, each write - will not be followed by a flush. In general, skipping the - flush operation improves logging throughput by roughly 15%. - The downside is that if the application exits abruptly, the - unwritten characters buffered inside the <code>Writer</code> - might be lost. This can be particularly troublesome as those - unwritten characters may contain crucial information needed in - identifying the reasons behind a crash. By default, the ImmediateFlush option is set to true. + <td>If the ImmediateFlush option is + set to true, then each write of a logging event will be followed + by a flush operation on the underlying <code>Writer</code> + object. Conversely, if the option is set to false, each write + will not be followed by a flush. In general, skipping the flush + operation improves logging throughput by roughly 15%. The + downside is that if the application exits abruptly, the + unwritten characters buffered inside the <code>Writer</code> + might be lost. This can be particularly troublesome as those + unwritten characters may contain crucial information needed in + identifying the reasons behind a crash. By default, the ImmediateFlush option is set to true. </td> </tr> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Tue Sep 11 21:01:05 2007 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.8</version> + <version>0.9.9-SNAPSHOT</version> <packaging>pom</packaging> <name>Logback-Parent</name>

1 0

implied Throwables
by Glen Marchesani 11 Sep '07

11 Sep '07

I love the project and am glad to see the new features added to logging in general. I am willing to write a patch for a feature but before I do I want to make sure it is something you would be interested in. There is no way to get a stack trace when using paramterized logging. The patch I want to add is that if the last parameter is a Throwable then it gets passed to the fitlerAndLog() method as a thorable (instead of throwable being null). To explain in code. log.debug( "Something happened parm1={} parm2={} parm3={}", 1, 2, 3, new Throwable() ); This would not cause the Throwable to be logged. So here are my questions - if I added the code to ch.qos.logback.classic.Logger is that something you are interested in? - lacking that any recommendations on how to get this feature built in. Looking forward to your comments and thanks for the great work on a great logging framework... regards, Glen

3 4

svn commit: r1588 - logback/trunk/logback-examples/src/main/java/chapter7
by noreply.ceki＠qos.ch 06 Sep '07

06 Sep '07

Author: ceki Date: Thu Sep 6 19:37:22 2007 New Revision: 1588 Modified: logback/trunk/logback-examples/src/main/java/chapter7/UserServletFilter.java Log: minor comment change Modified: logback/trunk/logback-examples/src/main/java/chapter7/UserServletFilter.java ============================================================================== --- logback/trunk/logback-examples/src/main/java/chapter7/UserServletFilter.java (original) +++ logback/trunk/logback-examples/src/main/java/chapter7/UserServletFilter.java Thu Sep 6 19:37:22 2007 @@ -61,7 +61,8 @@ HttpServletRequest req = (HttpServletRequest) request; Principal principal = req.getUserPrincipal(); - // we could have also used a cookie to retreive the user name + // Please note that we could have also used a cookie to + // retreive the user name if (principal != null) { String username = principal.getName();

1 0

svn commit: r1587 - logback/trunk/logback-site/src/site/pages
by noreply.ceki＠qos.ch 06 Sep '07

06 Sep '07

Author: ceki Date: Thu Sep 6 19:30:08 2007 New Revision: 1587 Modified: logback/trunk/logback-site/src/site/pages/news.html Log: so long retro-weaver 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 Thu Sep 6 19:30:08 2007 @@ -38,6 +38,12 @@ 64</a> and independently by Peter Huber. + Logback no longer includes retro-weaver generted jars for JDK + 1.4. There seemes to be little interest in JDK 1.4 builds. Calling + retro-weaver increases logback's build time by a few seconds each + time – seconds in which we can do more productive things. + + <hr width="80%" align="center" />

1 0

svn commit: r1586 - logback/trunk/logback-classic/src/test/resources/input
by noreply.ceki＠qos.ch 06 Sep '07

06 Sep '07

Author: ceki Date: Thu Sep 6 15:56:28 2007 New Revision: 1586 Removed: logback/trunk/logback-classic/src/test/resources/input/ Log: delete unused files

1 0