October 2010 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBSITE-38) Reference the configuration chapter from onJoran and vice versa
by Ceki Gulcu (JIRA) 11 Jan '11

11 Jan '11

Reference the configuration chapter from onJoran and vice versa --------------------------------------------------------------- Key: LBSITE-38 URL: http://jira.qos.ch/browse/LBSITE-38 Project: logback-site Issue Type: Task Components: Documentation Reporter: Ceki Gulcu Assignee: Logback dev list The onJoran chapter provides low level details about joran and the configuration chapter shows usage of joran. each chapter should reference the other for completeness. -- 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

[JIRA] Created: (LBCORE-160) TimeBasedRollingWithArchiveRemovalTest keeps failing
by Joern Huxhorn (JIRA) 29 Dec '10

29 Dec '10

TimeBasedRollingWithArchiveRemovalTest keeps failing ---------------------------------------------------- Key: LBCORE-160 URL: http://jira.qos.ch/browse/LBCORE-160 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: unspecified Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac" Reporter: Joern Huxhorn Assignee: Logback dev list Revision: 15b5239b5d583a86877b79e77336729317cf2dc0 The following error happens every time I try to build Logback: dailySizeBasedRollover(ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.443 sec <<< ERROR! java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:228) at java.util.concurrent.FutureTask.get(FutureTask.java:91) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.waitForCompression(TimeBasedRollingWithArchiveRemovalTest.java:216) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.doRollover(TimeBasedRollingWithArchiveRemovalTest.java:206) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.dailySizeBasedRollover(TimeBasedRollingWithArchiveRemovalTest.java:146) 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.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) 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:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 1

[JIRA] Created: (LBCLASSIC-113) Nullpointer
by Mathias Bogaert (JIRA) 23 Dec '10

23 Dec '10

Nullpointer ----------- Key: LBCLASSIC-113 URL: http://jira.qos.ch/browse/LBCLASSIC-113 Project: logback-classic Issue Type: Bug Components: Other Reporter: Mathias Bogaert Assignee: Logback dev list Priority: Critical java.lang.NullPointerException at ch.qos.logback.classic.Logger.callTurboFilters(Logger.java:769) [logback-classic-0.9.15.jar:na] at ch.qos.logback.classic.Logger.isTraceEnabled(Logger.java:641) [logback-classic-0.9.15.jar:na] at ch.qos.logback.classic.Logger.isTraceEnabled(Logger.java:637) [logback-classic-0.9.15.jar:na] at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:198) [hibernate-core-3.3.0.SP1.jar:3.3.0.SP1] at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) [hibernate-core-3.3.0.SP1.jar:3.3.0.SP1] at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:905) [hibernate-core-3.3.0.SP1.jar:3.3.0.SP1] Hibernate calls if ( log.isTraceEnabled() ). -- 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

3 3

[JIRA] Created: (LBACCESS-10) Servlet input stream gets corrupted
by Augusto (JIRA) 16 Nov '10

16 Nov '10

Servlet input stream gets corrupted ----------------------------------- Key: LBACCESS-10 URL: http://jira.qos.ch/browse/LBACCESS-10 Project: logback-access Issue Type: Bug Components: Other Affects Versions: 0.9.17 Environment: Windows 7 - java 1.6.0_16-b01 - Hightide 6.1H10 Windows 7 - java 1.6.0_16-b01 - Tomcat 6.0.16 Solaris 5.10 - java 1.6.0_16 - Hightide 6.1H10 Reporter: Augusto Assignee: Logback dev list The request.inputStream() is wrapped in a TeeServletInputStreamm but this class fails to pass all the data in the original input stream to the servlets. In my tests is passes properly between 4 and 8kb of data and later it just return zeros instead of the characters. I'm attaching a very simple webapp that writes the input stream of a POST request into a file to demonstrate the bug. -- 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 4

[JIRA] Created: (LBCORE-174) Add FromName to SMTPAppender
by Michael Osipov (JIRA) 08 Nov '10

08 Nov '10

Add FromName to SMTPAppender ---------------------------- Key: LBCORE-174 URL: http://jira.qos.ch/browse/LBCORE-174 Project: logback-core Issue Type: New Feature Components: Appender Affects Versions: unspecified Reporter: Michael Osipov Assignee: Logback dev list It is somewhat annoying that a received mail contains only the mail address in the from header. I'd like to a FromName. The emails from be: Tomcat on Host xyz.domain.com <noreply(a)domain.com> -- 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 5

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.25-16-g5e51ada
by git-noreply＠pixie.qos.ch 27 Oct '10

27 Oct '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 5e51ada8f7bb344d6e16f3e0a5678353dc413ec4 (commit) from b53a0c2272fcf4497ad1cc1b44193bd0d2f09aaa (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=5e51ada8f7bb344d6e16f3e0… http://github.com/ceki/logback/commit/5e51ada8f7bb344d6e16f3e0a5678353dc413… commit 5e51ada8f7bb344d6e16f3e0a5678353dc413ec4 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Oct 27 19:43:05 2010 +0200 added link to XtremeMP project diff --git a/logback-site/src/site/pages/index.html b/logback-site/src/site/pages/index.html index 36df255..0988a9c 100644 --- a/logback-site/src/site/pages/index.html +++ b/logback-site/src/site/pages/index.html @@ -95,6 +95,7 @@ dm Server</a></li> <li><a href="http://www.streambase.com/developers/docs/latest/index.html">StreamBase</a></li> <li><a href="http://www.eclipse.org/virgo/">Virgo Web Server</a></li> + <li><a href="http://xtrememp.sourceforge.net/">XtremeMP</a></li> <li><a href="http://www.xuggle.com/xuggler/">Xuggler</a></li> </ul> </td> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/index.html | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCORE-176) Document usage of RolligingFileAppedner without specifying a File property
by Ceki Gulcu (JIRA) 27 Oct '10

27 Oct '10

Document usage of RolligingFileAppedner without specifying a File property -------------------------------------------------------------------------- Key: LBCORE-176 URL: http://jira.qos.ch/browse/LBCORE-176 Project: logback-core Issue Type: Task Reporter: Ceki Gulcu Assignee: Logback dev list Relates to -- 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 3

Problem with Syslog appender
by Pradnya Gawade 25 Oct '10

25 Oct '10

Hi, I have following requirements when sending the log from a java web application to syslog server: 1. When logging the stack trace in case of exceptions, all the stack strace should be seen as a single message. 2. Need to send either or all of the following information in logs- name of the web application, URL, version of the application. As per my knowledge, Syslog appender of Logback doesnot fit to above requirements. I am also looking for any other logging APIs which can satisfy these requirements. Any ideas? Thanks in advance. - Pradnya

2 1

[JIRA] Created: (LBCORE-170) CyclicBufferTrackerImpl.setBufferSize doesn't modify the field
by peter royal (JIRA) 21 Oct '10

21 Oct '10

CyclicBufferTrackerImpl.setBufferSize doesn't modify the field -------------------------------------------------------------- Key: LBCORE-170 URL: http://jira.qos.ch/browse/LBCORE-170 Project: logback-core Issue Type: Bug Components: Other Affects Versions: 0.9.24 Reporter: peter royal Assignee: Logback dev list The setBufferSize method on CyclicBufferTrackerImpl doesn't actually modify the field, making it impossible to shrink the buffer. -- 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 7

[JIRA] Created: (LBCORE-175) Provide default value for MDC values in pattern layout
by Michael Osipov (JIRA) 21 Oct '10

21 Oct '10

Provide default value for MDC values in pattern layout ------------------------------------------------------ Key: LBCORE-175 URL: http://jira.qos.ch/browse/LBCORE-175 Project: logback-core Issue Type: Improvement Components: Pattern Affects Versions: 0.9.24 Reporter: Michael Osipov Assignee: Logback dev list I am logging the user principal and not every request has to be authenticated. I set in my pattern layout: %X{req.userPrincipal:-unauthenticated} It did not work of course. Please make default values possible for MDC values just like for properties. -- 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