- logback-dev - mailman3.qos.ch

branch, master, updated. a2eb7c52b0312856e6f4c67670a4a11df4272780
by git-noreply＠pixie.qos.ch 28 Oct '09

28 Oct '09

The branch, master has been updated via a2eb7c52b0312856e6f4c67670a4a11df4272780 (commit) from 392672023cda2281b905c62f730cdd3b585aa853 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=a2eb7c52b0312856e6f4c676… http://github.com/ceki/logback/commit/a2eb7c52b0312856e6f4c67670a4a11df4272… commit a2eb7c52b0312856e6f4c67670a4a11df4272780 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Oct 28 22:54:50 2009 +0100 - Applied http://github.com/cehjohnson/logback/commit/2194ab44141abed25479ec00e4a88b4… from October 04, 2009 However, the ">" to ">" transformation has been ignored and will continue to be so in the future. diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index f725cf7..3971387 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -64,14 +64,14 @@ Inserting log requests into the application code requires a fair amount of planning and effort. Observation shows that approximately four percent of code is dedicated to - logging. Consequently, even moderately sized applications will + logging. Consequently, even a moderately sized application will contain thousands of logging statements embedded within its code. Given their number, we need tools to manage these log statements. - Logback can be configured either programmatically or with - configuration a script (expressed in XML format). By the way, + Logback can be configured either programmatically or with a + configuration script (expressed in XML format). By the way, existing log4j users can convert their log4j.properties files to logback.xml using our <a href="http://logback.qos.ch/translator/">PropertiesTranslator</a> @@ -124,7 +124,7 @@ <h3>Automatically configuring logback</h3> The simplest way to configure logback is by letting logback - fallback to its default configuration. Let us give a taste of how + fall back to its default configuration. Let us give a taste of how this is done in an imaginary application called <code>MyApp1</code>. @@ -213,8 +213,8 @@ public class Foo { The <code>MyApp1</code> application links to logback via calls <code>org.slf4j.LoggerFactory</code> and <code>org.slf4j.Logger</code> classes, retrieve the loggers it - wishes to use, and chugs on. Note that the only dependence of the - <code>Foo</code> class on logback are through + wishes to use, and chugs on. Note that the only dependencies of + the <code>Foo</code> class on logback are through <code>org.slf4j.LoggerFactory</code> and <code>org.slf4j.Logger</code> imports. Except code that configures logback (if such code exists) client code does not need to depend @@ -350,14 +350,14 @@ public class Foo { <li>the configuration file is well-formed XML.</li> </ol> - If any of these two conditions is not fulfilled, the Joran - cannot interpret <code>debug</code> attribute since the - configuration file cannot be read. If the configuration file is - found but is ill-formed, then logback will detect the error - condition and automatically print its internal status on the - console. However, if the configuration file cannot be found, since - this is not necessarily an error condition, logback will not - automatically print its status data. Programmatically invoking + If any of these two conditions is not fulfilled, Joran cannot + interpret <code>debug</code> attribute since the configuration file + cannot be read. If the configuration file is found but is + ill-formed, then logback will detect the error condition and + automatically print its internal status on the console. However, if + the configuration file cannot be found, since this is not + necessarily an error condition, logback will not automatically + print its status data. Programmatically invoking <code>StatusPrinter.print()</code>, as as in MyApp2 application above, ensures that status information is always printed. @@ -462,7 +462,7 @@ public class Foo { override logback's default configuration mechanism, you can do so by invoking <code>JoranConfigurator</code> directly. The next application, MyApp3, invokes JoranConfigurator on a - configuration file passed as parameter. + configuration file passed as a parameter. Example 3.: Invoking <code>JoranConfigurator</code> directly <a @@ -528,7 +528,7 @@ public class MyApp3 { Given a <code>StatusManager</code> you an access all the status data associated with a logback context. To keep memory usage at reasonable levels, the default <code>StatusManager</code> - implementation stores the status messages in two separate parts, + implementation stores the status messages in two separate parts: the header part and the tail part. The header part stores the fist H status messages whereas the tail part stores the last T messages. At present time H=T=150, @@ -585,7 +585,7 @@ public class MyApp3 { Here is <a href="../xref/chapter3/AddStatusListenerApp.html">sample code</a> - to register a OnConsoleStatusListener instance with the + to register an OnConsoleStatusListener instance with the StatusManager. @@ -637,12 +637,12 @@ public class MyApp3 { As shall become clear, the syntax of logback configuration files - is extremely flexible. As such, it is not possible specify the - allowed syntax with a DTD file or an XML Schema. Nevertheless, the - very basic structure of configuration can be described as, + is extremely flexible. As such, it is not possible to specify the + allowed syntax with a DTD file or an XML schema. Nevertheless, the + very basic structure of the configuration file can be described as, <configuration> element, followed by zero or more <appender> - elements, followed by by zero or more <logger> elements, followed - by at most one <root> element. The following diagram illustrates + elements, followed by zero or more <logger> elements, followed by + at most one <root> element. The following diagram illustrates this basic structure. diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index f8b0581..90259f0 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -193,7 +193,7 @@ public class HelloWorld2 { larger application would not be that different. The general pattern for logging statements would not change. Only the configuration process would be different. However, you would probably want to - customize or configure logback according to your needs. Logback + customize or configure logback according to your needs. Logback configuration will be covered in subsequent chapters. ----------------------------------------------------------------------- Summary of changes: .../src/site/pages/manual/configuration.html | 44 ++++++++++---------- .../src/site/pages/manual/introduction.html | 2 +- 2 files changed, 23 insertions(+), 23 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

branch, master, updated. 392672023cda2281b905c62f730cdd3b585aa853
by git-noreply＠pixie.qos.ch 28 Oct '09

28 Oct '09

The branch, master has been updated via 392672023cda2281b905c62f730cdd3b585aa853 (commit) from 33dfb1600acd3d5e2c6f98e4f471be8ac3d796e2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=392672023cda2281b905c62f… http://github.com/ceki/logback/commit/392672023cda2281b905c62f730cdd3b585aa… commit 392672023cda2281b905c62f730cdd3b585aa853 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Oct 28 22:27:35 2009 +0100 - applied cehjohnson's commit f257e840947c41c6ae5c5ed182e7ccb5c3ffd640 from October 02, 2009 diff --git a/logback-site/src/site/pages/manual/architecture.html b/logback-site/src/site/pages/manual/architecture.html index b1e7c31..6d353c3 100644 --- a/logback-site/src/site/pages/manual/architecture.html +++ b/logback-site/src/site/pages/manual/architecture.html @@ -44,7 +44,7 @@ <h2>Logback's architecture</h2> Logback's basic architecture is sufficiently generic so as to - apply under different circumstances. At present time, logback is + apply under different circumstances. At the present time, logback is divided into three modules, Core, Classic and Access. @@ -150,7 +150,7 @@ public interface Logger { that is TRACE, DEBUG, INFO, WARN and ERROR are defined in the <code>ch.qos.logback.classic.Level</code> class. Note that in logback, the level class is final and cannot be derived, as a much - more flexible approach exist in the form of <code>Marker</code> + more flexible approach exists in the form of <code>Marker</code> objects. @@ -244,7 +244,7 @@ public interface Logger { </table> In example 2 above, all loggers have an assigned level value. - Level inheritence does not come into play. + Level inheritance does not come into play. Example 3 @@ -358,7 +358,7 @@ public interface Logger { In a more graphic way, here is how the selection rule works. In - the following table, the vertical header shows the the level of + the following table, the vertical header shows the level of the logging request, designated by p, while the horizontal header shows effective level of the logger, designated by q. The intersection of the rows (level request) and @@ -541,8 +541,8 @@ Logger y = LoggerFactory.getLogger("wombat");</pre> However, if an ancestor of logger L, say P, has the additivity flag set to false, then L's output - will be directed to all the appenders in L and it's - ancestors upto and including P but not the appenders in + will be directed to all the appenders in L and its + ancestors up to and including P but not the appenders in any of the ancestors of P. @@ -727,7 +727,7 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> <a name="UnderTheHood"></a> - <h3>A peak under the hood</h3> + <h3>A peek under the hood</h3> After we have introduced the essential logback components, we are now ready to describe the steps that the logback framework takes @@ -762,7 +762,7 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> <h4>3. Create a <code>LoggingEvent</code> object</h4> - If the request survivedy the previous filters, logback will + If the request survived the previous filters, logback will create a <code>ch.qos.logback.classic.LoggingEvent</code> object containing all the relevant parameters of the request, such as the logger of the request, the request level, the message itself, the @@ -854,7 +854,7 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> The cost of parameter construction can be quite high and depends on the size of the parameters involved. To avoid the cost of - parameter construction you can take advantage of SLF4J's parametrized + parameter construction you can take advantage of SLF4J's parameterized logging: @@ -872,9 +872,9 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> Please notice that, despite the performance points that we just - discussed, inserting logging statements in tight-loops or very + discussed, inserting logging statements in tight loops or very frequently invoked code is a lose-lose proposal and is likely to - result in degraded performance. Logging in tight-loops slow down + result in degraded performance. Logging in tight loops slow down your application even if logging is turned off, and if logging is turned on, they will generate massive (and hence useless) output. diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index 3d7a2d0..f8b0581 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -123,12 +123,12 @@ public class HelloWorld1 { You can launch the first - sample application, chapter1.HelloWord1 with the command: + sample application, chapter1.HelloWorld1 with the command: <div class="source"><pre>java chapter1.HelloWorld1</pre></div> Launching the <code>HelloWorld1</code> application will output - a single line on the console. By virtue of to logback's default + a single line on the console. By virtue of logback's default configuration policy, when no default configuration file is found, logback will add a <code>ConsoleAppender</code> to the root logger. @@ -191,9 +191,9 @@ public class HelloWorld2 { The previous examples are rather simple. Actual logging in a larger application would not be that different. The general pattern - for logging statements would not change. nly the configuration - process would be different since However, you would probably want to - customize or configure logback for according to your needs. Logback + for logging statements would not change. Only the configuration + process would be different. However, you would probably want to + customize or configure logback according to your needs. Logback configuration will be covered in subsequent chapters. @@ -216,7 +216,7 @@ public class HelloWorld2 { <code>Logger</code> instance by invoking the <code>org.slf4j.LoggerFactory</code> class' <code>getLogger()</code> method, passing the current class name - or the class itself as parameter.</li> + or the class itself as a parameter.</li> <li>Use this logger instance by invoking its printing methods, namely the debug(), info(), warn() and error(). This will ----------------------------------------------------------------------- Summary of changes: .../src/site/pages/manual/architecture.html | 22 ++++++++++---------- .../src/site/pages/manual/introduction.html | 12 +++++----- 2 files changed, 17 insertions(+), 17 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-163) LoggingEventVO does not serialize the argument array properly.
by Ralph Goers (JIRA) 26 Oct '09

26 Oct '09

LoggingEventVO does not serialize the argument array properly. -------------------------------------------------------------- Key: LBCLASSIC-163 URL: http://jira.qos.ch/browse/LBCLASSIC-163 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.917 Reporter: Ralph Goers Assignee: Logback dev list LoggingEventVO serializes the objects in the argument array by simply calling toString(). This makes it impossible to reconstruct the objects on the remote side. I have fixed this in my fork at git://github.com/rgoers/logback.git by serializing the object if it implements Serializable and converting it to a String if it does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

4 14

[JIRA] Created: (LBCLASSIC-164) Make the aspect of encoding a LoggingEvent pluggable, and thus the Appender implementation more reusable.
by Maarten Bosteels (JIRA) 24 Oct '09

24 Oct '09

Make the aspect of encoding a LoggingEvent pluggable, and thus the Appender implementation more reusable. --------------------------------------------------------------------------------------------------------- Key: LBCLASSIC-164 URL: http://jira.qos.ch/browse/LBCLASSIC-164 Project: logback-classic Issue Type: New Feature Components: appender Reporter: Maarten Bosteels Assignee: Logback dev list Refactor the encoding out of appender implementations, by adding an Encoder interface to logback. prototype: http://code.google.com/p/firewood/source/browse/trunk/compare-formats/src/m… -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 1

LoggingEventVO and serialization
by Ralph Goers 22 Oct '09

22 Oct '09

I am going to be creating a logging service. The architecture in our POC is the client uses the JMSTopicAppender writing to ActiveMQ and then the service will listen on the topic and write to the destination. To avoid having the messages be logback specific so that our legacy system can also interact with this I will be serializing the messages according the the IETFSyslogLayout in my fork of Logback (i.e. all the messages will comply with RFC 5424). I got this working today with the output temporarily going to syslog-ng (which supports IETF syslog messages). Of Course, JMSTopicAppender and JMSQueueAppender had to be modified to allow a different form of serialization. This was easily done by just seeing if a layout was configured. If so, then LayoutPreSerializationTransformer is used instead of LoggingEventPreSerializationTransformer. However, just for fun I tried serializing to LoggingEventVO using the default mechanisms in place and sending that through the JMS Appender to the JMSTopicSink. It didn't quite work correctly. In looking at why I discovered the LoggingEventVO serializes arguments by calling toString(). So when the JMSAppender transforms the objects their object type is lost. This means on the remote side it is impossible to convert them back to the original object. I would think that some form of the Serialized object should be in the argument array instead of just a String. Otherwise it is impossible to get the remote side to behave like the original client. Ralph

1 0

[JIRA] Created: (LBGENERAL-33) SMTPAppender_SubethaSMTPTest hang
by Ralph Goers (JIRA) 21 Oct '09

21 Oct '09

SMTPAppender_SubethaSMTPTest hang --------------------------------- Key: LBGENERAL-33 URL: http://jira.qos.ch/browse/LBGENERAL-33 Project: logback-general Issue Type: Sub-task Affects Versions: 0.9.17 Environment: Mac OSX Reporter: Ralph Goers Assignee: Logback dev list This test frequently waits forever waiting for a response. The jstack output follows: 2009-10-13 09:59:33 Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.1-b02-90 mixed mode): "Attach Listener" daemon prio=9 tid=0x00000001022f4800 nid=0x1150c6000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "SocketAcceptorIoProcessor-2.0" prio=5 tid=0x000000011316f000 nid=0x115487000 runnable [0x0000000115486000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.KQueueArrayWrapper.kevent0(Native Method) at sun.nio.ch.KQueueArrayWrapper.poll(KQueueArrayWrapper.java:136) at sun.nio.ch.KQueueSelectorImpl.doSelect(KQueueSelectorImpl.java:69) at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69) - locked <0x00000001064d86b8> (a sun.nio.ch.Util$1) - locked <0x00000001064d86a0> (a java.util.Collections$UnmodifiableSet) - locked <0x00000001064d8340> (a sun.nio.ch.KQueueSelectorImpl) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) at org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(SocketIoProcessor.java:480) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) "SocketAcceptor-2" prio=5 tid=0x0000000102196800 nid=0x114e4e000 runnable [0x0000000114e4d000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.KQueueArrayWrapper.kevent0(Native Method) at sun.nio.ch.KQueueArrayWrapper.poll(KQueueArrayWrapper.java:136) at sun.nio.ch.KQueueSelectorImpl.doSelect(KQueueSelectorImpl.java:69) at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69) - locked <0x0000000107ad72c0> (a sun.nio.ch.Util$1) - locked <0x0000000107ad72d8> (a java.util.Collections$UnmodifiableSet) - locked <0x0000000107aee2b8> (a sun.nio.ch.KQueueSelectorImpl) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:84) at org.apache.mina.transport.socket.nio.SocketAcceptor$Worker.run(SocketAcceptor.java:220) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) "HSQLDB Timer @e8ae59a" daemon prio=5 tid=0x0000000113421800 nid=0x114fc3000 in Object.wait() [0x0000000114fc2000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000001072e8c08> (a org.hsqldb.lib.HsqlTimer) at org.hsqldb.lib.HsqlTimer.nextTask(Unknown Source) - locked <0x00000001072e8c08> (a org.hsqldb.lib.HsqlTimer) at org.hsqldb.lib.HsqlTimer$TaskRunner.run(Unknown Source) at java.lang.Thread.run(Thread.java:637) "Thread-5" prio=5 tid=0x00000001023ac800 nid=0x114b1b000 runnable [0x0000000114b1a000] java.lang.Thread.State: RUNNABLE at java.net.PlainDatagramSocketImpl.receive0(Native Method) - locked <0x00000001071a3c58> (a java.net.PlainDatagramSocketImpl) at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) - locked <0x00000001071a3c58> (a java.net.PlainDatagramSocketImpl) at java.net.DatagramSocket.receive(DatagramSocket.java:712) - locked <0x00000001071c6cd8> (a java.net.DatagramPacket) - locked <0x0000000107195e18> (a java.net.DatagramSocket) at ch.qos.logback.classic.net.mock.MockSyslogServer.run(MockSyslogServer.java:50) "Thread-4" prio=5 tid=0x000000011321f800 nid=0x114a18000 runnable [0x0000000114a17000] java.lang.Thread.State: RUNNABLE at java.net.PlainDatagramSocketImpl.receive0(Native Method) - locked <0x00000001071a3cb0> (a java.net.PlainDatagramSocketImpl) at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) - locked <0x00000001071a3cb0> (a java.net.PlainDatagramSocketImpl) at java.net.DatagramSocket.receive(DatagramSocket.java:712) - locked <0x00000001071c6d08> (a java.net.DatagramPacket) - locked <0x0000000107195e50> (a java.net.DatagramSocket) at ch.qos.logback.classic.net.mock.MockSyslogServer.run(MockSyslogServer.java:50) "Thread-3" prio=5 tid=0x000000010241d800 nid=0x114915000 runnable [0x0000000114914000] java.lang.Thread.State: RUNNABLE at java.net.PlainDatagramSocketImpl.receive0(Native Method) - locked <0x0000000107104030> (a java.net.PlainDatagramSocketImpl) at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) - locked <0x0000000107104030> (a java.net.PlainDatagramSocketImpl) at java.net.DatagramSocket.receive(DatagramSocket.java:712) - locked <0x0000000107125850> (a java.net.DatagramPacket) - locked <0x00000001071243f8> (a java.net.DatagramSocket) at ch.qos.logback.classic.net.mock.MockSyslogServer.run(MockSyslogServer.java:50) "Thread-1" prio=5 tid=0x000000011316c000 nid=0x114703000 runnable [0x0000000114702000] java.lang.Thread.State: RUNNABLE at java.net.PlainDatagramSocketImpl.receive0(Native Method) - locked <0x0000000107077898> (a java.net.PlainDatagramSocketImpl) at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) - locked <0x0000000107077898> (a java.net.PlainDatagramSocketImpl) at java.net.DatagramSocket.receive(DatagramSocket.java:712) - locked <0x00000001070e9668> (a java.net.DatagramPacket) - locked <0x00000001070f1b20> (a java.net.DatagramSocket) at ch.qos.logback.classic.net.mock.MockSyslogServer.run(MockSyslogServer.java:50) "Thread-0" prio=5 tid=0x0000000113113000 nid=0x1145ed000 runnable [0x00000001145ec000] java.lang.Thread.State: RUNNABLE at java.net.PlainDatagramSocketImpl.receive0(Native Method) - locked <0x00000001070778f0> (a java.net.PlainDatagramSocketImpl) at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) - locked <0x00000001070778f0> (a java.net.PlainDatagramSocketImpl) at java.net.DatagramSocket.receive(DatagramSocket.java:712) - locked <0x00000001070e9698> (a java.net.DatagramPacket) - locked <0x00000001070f1b58> (a java.net.DatagramSocket) at ch.qos.logback.classic.net.mock.MockSyslogServer.run(MockSyslogServer.java:50) "Low Memory Detector" daemon prio=5 tid=0x000000010208e000 nid=0x114290000 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "CompilerThread1" daemon prio=9 tid=0x000000010208d800 nid=0x11418d000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "CompilerThread0" daemon prio=9 tid=0x000000010208c800 nid=0x11408a000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" daemon prio=9 tid=0x000000010208c000 nid=0x113f87000 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Surrogate Locker Thread (CMS)" daemon prio=5 tid=0x000000010208b000 nid=0x113e84000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Finalizer" daemon prio=8 tid=0x0000000102075800 nid=0x113b07000 in Object.wait() [0x0000000113b06000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0000000106ef0848> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118) - locked <0x0000000106ef0848> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) "Reference Handler" daemon prio=10 tid=0x0000000113026000 nid=0x113a04000 in Object.wait() [0x0000000113a03000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0000000106ef0860> (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:485) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) - locked <0x0000000106ef0860> (a java.lang.ref.Reference$Lock) "main" prio=5 tid=0x0000000102000800 nid=0x101301000 runnable [0x00000001012fe000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:97) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) - locked <0x0000000106458610> (a java.io.BufferedInputStream) at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:75) at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1440) at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1376) at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTransport.java:1215) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:586) - locked <0x0000000106454d10> (a com.sun.mail.smtp.SMTPTransport) at javax.mail.Transport.send0(Transport.java:169) at javax.mail.Transport.send(Transport.java:98) at ch.qos.logback.core.net.SMTPAppenderBase.sendBuffer(SMTPAppenderBase.java:282) at ch.qos.logback.core.net.SMTPAppenderBase.append(SMTPAppenderBase.java:153) at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:91) - locked <0x000000010710e350> (a ch.qos.logback.classic.net.SMTPAppender) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:276) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:263) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:445) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:399) at ch.qos.logback.classic.Logger.error(Logger.java:562) at ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest.htmlLong(SMTPAppender_SubethaSMTPTest.java:195) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) "VM Thread" prio=9 tid=0x0000000102070000 nid=0x113901000 runnable "Gang worker#0 (Parallel GC Threads)" prio=9 tid=0x0000000102002000 nid=0x105902000 runnable "Gang worker#1 (Parallel GC Threads)" prio=9 tid=0x0000000102002800 nid=0x105a05000 runnable "Concurrent Mark-Sweep GC Thread" prio=9 tid=0x0000000102042000 nid=0x112d9f000 runnable "VM Periodic Task Thread" prio=10 tid=0x000000010208f000 nid=0x114393000 waiting on condition "Exception Catcher Thread" prio=10 tid=0x0000000102001800 nid=0x101701000 runnable JNI global references: 939 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 1

branch, master, updated. 33dfb1600acd3d5e2c6f98e4f471be8ac3d796e2
by git-noreply＠pixie.qos.ch 16 Oct '09

16 Oct '09

The branch, master has been updated via 33dfb1600acd3d5e2c6f98e4f471be8ac3d796e2 (commit) from 7746ef887110ae043226be2b6cc78c7c28b66df8 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=33dfb1600acd3d5e2c6f98e4… http://github.com/ceki/logback/commit/33dfb1600acd3d5e2c6f98e4f471be8ac3d79… commit 33dfb1600acd3d5e2c6f98e4f471be8ac3d796e2 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Oct 16 21:01:43 2009 +0200 logback-announce replaced by announce(a)qos.ch diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 98c64be..a0e1217 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -23,8 +23,7 @@ <h2>Logback News</h2> You can receive logback-related announcements by subscribing to - the <a - href="http://www.qos.ch/mailman/listinfo/logback-announce">logback + the <a href="http://www.qos.ch/mailman/listinfo/announce">QOS.ch announce</a> mailing list. <hr width="80%" align="center" /> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/news.html | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

branch, master, updated. 7746ef887110ae043226be2b6cc78c7c28b66df8
by git-noreply＠pixie.qos.ch 16 Oct '09

16 Oct '09

The branch, master has been updated via 7746ef887110ae043226be2b6cc78c7c28b66df8 (commit) via 23abd09c563b9f6c84716d5c17005db9f5f3ebc4 (commit) from d3e8a64dce1edb3c769101d874cae1f090f3021b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=7746ef887110ae043226be2b… http://github.com/ceki/logback/commit/7746ef887110ae043226be2b6cc78c7c28b66… commit 7746ef887110ae043226be2b6cc78c7c28b66df8 Merge: 23abd09 d3e8a64 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Oct 16 18:50:27 2009 +0200 Merge branch 'master' of git.qos.ch:logback http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=23abd09c563b9f6c84716d5c… http://github.com/ceki/logback/commit/23abd09c563b9f6c84716d5c17005db9f5f3e… commit 23abd09c563b9f6c84716d5c17005db9f5f3ebc4 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Oct 16 18:50:15 2009 +0200 merged logback-announce into announce(a)qos.ch diff --git a/logback-site/src/site/pages/mailinglist.html b/logback-site/src/site/pages/mailinglist.html index 7a7268b..c03f6fe 100644 --- a/logback-site/src/site/pages/mailinglist.html +++ b/logback-site/src/site/pages/mailinglist.html @@ -62,33 +62,25 @@ <th>Archives</th> </tr> <tr class="b"> - <td>Logback Announce List</td> + <td>QOS.ch announce List</td> <td>Low</td> <td> <a - href="http://qos.ch/mailman/listinfo/logback-announce"> + href="http://qos.ch/mailman/listinfo/announce"> Subscribe </a> </td> <td> <a - href="http://qos.ch/mailman/options/logback-announce"> + href="http://qos.ch/mailman/options/announce"> Unsubscribe </a> </td> <td> <a - href="http://www.qos.ch/pipermail/logback-announce/"> + href="http://www.qos.ch/pipermail/announce/"> qos.ch - </a> | - <a - href="http://marc.theaimsgroup.com/?l=logback-announce"> - MARC - </a> | - <a - href="http://www.nabble.com/Logback-Announce-f16251.html"> - Nabble - </a> + </a> </td> </tr> <tr class="a"> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/mailinglist.html | 18 +++++------------- 1 files changed, 5 insertions(+), 13 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-162) Typo in ClassicConstants
by Joern Huxhorn (JIRA) 15 Oct '09

15 Oct '09

Typo in ClassicConstants ------------------------ Key: LBCLASSIC-162 URL: http://jira.qos.ch/browse/LBCLASSIC-162 Project: logback-classic Issue Type: Improvement Components: Other Affects Versions: 0.917 Reporter: Joern Huxhorn Assignee: Logback dev list Priority: Minor ch.qos.logback.classic.ClassicConstants.DEFAULT_MAX_CALLEDER_DATA_DEPTH should be DEFAULT_MAX_CALLER_DATA_DEPTH. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

Some documentation shortcomings and a typo...
by Joern Huxhorn 15 Oct '09

15 Oct '09

Hi Ceki, I just realized that the documentation is missing info about how to disable packaging data and how to set maxCallerDataDepth. I wasn't able to find it, at least. On a side note, I also saw that there's a typo in ClassicConstants.DEFAULT_MAX_CALLEDER_DATA_DEPTH ;) Regards, Joern.

2 2