- logback-dev - mailman3.qos.ch

Dual licensing logback
by Ceki Gulcu 17 Sep '09

17 Sep '09

Hello all, After a very long investigation resulting in a better understanding of licensing issues, I think dual-licensing logback under EPL 1.0 and LGPL 2.1 would help with the project's adoption. Licensees can then choose either the terms of the EPL or the terms of the LGPL when they use logback. The EPL license will placate organizations which refuse the restrictions imposed by the LGPL whereas the LGPL license ensures continuity in licensing and also keeps the door open for licensees already bound by the terms of (L)GPL. Comments? ps. If you intend to respond, please do so on logback-users@. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

[JIRA] Issue Comment Edited: (LBCORE-26) TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file.
by Ceki Gulcu (JIRA) 15 Sep '09

15 Sep '09

[ http://jira.qos.ch/browse/LBCORE-26?page=com.atlassian.jira.plugin.system.i… ] Ceki Gulcu edited comment on LBCORE-26 at 9/15/09 3:29 PM: ----------------------------------------------------------- Apparently this bug has resurfaced. See http://www.qos.ch/pipermail/logback-user/2009-September/001295.html <configuration scan="true"> <appender name="LOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/log/zeugma/selectterms/selectterms.log </file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>/var/log/zeugma/selectterms/selectterms.%d{yyyy-MM-dd}.log.gz</FileNamePattern> <MaxHistory>30</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger - %msg%n</Pattern> </layout> </appender> <root level="info"> <appender-ref ref="LOG" /> </root> </configuration> was (Author: noreply.ceki(a)qos.ch) Apparently this bug has resurfaced. See http://www.qos.ch/pipermail/logback-user/2009-September/001295.html > TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file. > ---------------------------------------------------------------------------------------- > > Key: LBCORE-26 > URL: http://jira.qos.ch/browse/LBCORE-26 > Project: logback-core > Issue Type: Bug > Components: Rolling > Affects Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Tsutomu YANO > Assignee: Ceki Gulcu > Priority: Critical > Fix For: 0.9.12 > > > If you use TimeBasedRollingPolicy to rollover a log file and no log wasn't wrote into the log beyond the timing of rollover, and if you restart your application, the log file doesn't roll, then new log will be appended into old log file. > EVIDENCE: > 1. in logback.xml, set your FileNamePattern like 'log.%d{yyyy-MM-dd_HH-mm}.log'. > 2. Simply do a kind of thing, which will make some logs into your log file. > 3. Wait for some minutes. > 4. restart your application. > 5. do a kind of thing, which will make some logs into your log file. > the FileNamePattern is 'log.%d{yyyy-MM-dd_HH-mm}.log', so the log file will be roll every minutes. On case 5 of above example, the log file should be roll over, because some minutes already have passed after last logs wrote into the log file. But the file didn't be roll overed. > THE CAUSE: > In start() method of TimeBasedRollingPolicy, you initialize a variable 'lastCheck' to System.currentTimeStamp(). So if you restart your application, the last check time will be set to just NOW. > you should initialize the variable to a last modified time of a current log file. > See below source code. from '//modified by Tsutomu YANO' to '//until here'. > SOURCE: > public void start() { > // set the LR for our utility object > util.setContext(this.context); > compress.setContext(this.context); > // find out period from the filename pattern > if (fileNamePatternStr != null) { > fileNamePattern = new FileNamePattern(fileNamePatternStr, this.context); > determineCompressionMode(); > } else { > addWarn(FNP_NOT_SET); > addWarn(SEE_FNP_NOT_SET); > throw new IllegalStateException(FNP_NOT_SET + SEE_FNP_NOT_SET); > } > DateTokenConverter dtc = fileNamePattern.getDateTokenConverter(); > if (dtc == null) { > throw new IllegalStateException("FileNamePattern [" + fileNamePattern.getPattern() + "] does not contain a valid DateToken"); > } > int len = fileNamePatternStr.length(); > switch (compressionMode) { > case Compress.GZ: > activeFileNamePattern = new FileNamePattern(fileNamePatternStr.substring(0, len - 3), this.context); > break; > case Compress.ZIP: > activeFileNamePattern = new FileNamePattern(fileNamePatternStr.substring(0, len - 4), this.context); > break; > case Compress.NONE: > activeFileNamePattern = fileNamePattern; > } > addInfo("Will use the pattern " + activeFileNamePattern + " for the active file"); > rc = new RollingCalendar(); > rc.init(dtc.getDatePattern()); > addInfo("The date pattern is '" + dtc.getDatePattern() + "' from file name pattern '" + fileNamePattern.getPattern() + "'."); > rc.printPeriodicity(this); > > //modified by Tsutomu YANO > //if a current log file exists, initialize a 'lastCheck' variable to the > //last modified date of the file. > File currentFile = new File(getParentFileName()); > if(currentFile.exists() && currentFile.canRead()) { > lastCheck.setTime(currentFile.lastModified()); > } else { > // currentTime = System.currentTimeMillis(); > lastCheck.setTime(getCurrentTime()); > } > //until here > > nextCheck = rc.getNextCheckMillis(lastCheck); > // Date nc = new Date(); > // nc.setTime(nextCheck); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Reopened: (LBCORE-26) TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file.
by Ceki Gulcu (JIRA) 15 Sep '09

15 Sep '09

[ http://jira.qos.ch/browse/LBCORE-26?page=com.atlassian.jira.plugin.system.i… ] Ceki Gulcu reopened LBCORE-26: ------------------------------ Apparently this bug has resurfaced. See http://www.qos.ch/pipermail/logback-user/2009-September/001295.html > TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file. > ---------------------------------------------------------------------------------------- > > Key: LBCORE-26 > URL: http://jira.qos.ch/browse/LBCORE-26 > Project: logback-core > Issue Type: Bug > Components: Rolling > Affects Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Tsutomu YANO > Assignee: Ceki Gulcu > Priority: Critical > Fix For: 0.9.12 > > > If you use TimeBasedRollingPolicy to rollover a log file and no log wasn't wrote into the log beyond the timing of rollover, and if you restart your application, the log file doesn't roll, then new log will be appended into old log file. > EVIDENCE: > 1. in logback.xml, set your FileNamePattern like 'log.%d{yyyy-MM-dd_HH-mm}.log'. > 2. Simply do a kind of thing, which will make some logs into your log file. > 3. Wait for some minutes. > 4. restart your application. > 5. do a kind of thing, which will make some logs into your log file. > the FileNamePattern is 'log.%d{yyyy-MM-dd_HH-mm}.log', so the log file will be roll every minutes. On case 5 of above example, the log file should be roll over, because some minutes already have passed after last logs wrote into the log file. But the file didn't be roll overed. > THE CAUSE: > In start() method of TimeBasedRollingPolicy, you initialize a variable 'lastCheck' to System.currentTimeStamp(). So if you restart your application, the last check time will be set to just NOW. > you should initialize the variable to a last modified time of a current log file. > See below source code. from '//modified by Tsutomu YANO' to '//until here'. > SOURCE: > public void start() { > // set the LR for our utility object > util.setContext(this.context); > compress.setContext(this.context); > // find out period from the filename pattern > if (fileNamePatternStr != null) { > fileNamePattern = new FileNamePattern(fileNamePatternStr, this.context); > determineCompressionMode(); > } else { > addWarn(FNP_NOT_SET); > addWarn(SEE_FNP_NOT_SET); > throw new IllegalStateException(FNP_NOT_SET + SEE_FNP_NOT_SET); > } > DateTokenConverter dtc = fileNamePattern.getDateTokenConverter(); > if (dtc == null) { > throw new IllegalStateException("FileNamePattern [" + fileNamePattern.getPattern() + "] does not contain a valid DateToken"); > } > int len = fileNamePatternStr.length(); > switch (compressionMode) { > case Compress.GZ: > activeFileNamePattern = new FileNamePattern(fileNamePatternStr.substring(0, len - 3), this.context); > break; > case Compress.ZIP: > activeFileNamePattern = new FileNamePattern(fileNamePatternStr.substring(0, len - 4), this.context); > break; > case Compress.NONE: > activeFileNamePattern = fileNamePattern; > } > addInfo("Will use the pattern " + activeFileNamePattern + " for the active file"); > rc = new RollingCalendar(); > rc.init(dtc.getDatePattern()); > addInfo("The date pattern is '" + dtc.getDatePattern() + "' from file name pattern '" + fileNamePattern.getPattern() + "'."); > rc.printPeriodicity(this); > > //modified by Tsutomu YANO > //if a current log file exists, initialize a 'lastCheck' variable to the > //last modified date of the file. > File currentFile = new File(getParentFileName()); > if(currentFile.exists() && currentFile.canRead()) { > lastCheck.setTime(currentFile.lastModified()); > } else { > // currentTime = System.currentTimeMillis(); > lastCheck.setTime(getCurrentTime()); > } > //until here > > nextCheck = rc.getNextCheckMillis(lastCheck); > // Date nc = new Date(); > // nc.setTime(nextCheck); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (LBSITE-33) Typo in Configuring Loggers documentation
by Mark Vedder (JIRA) 11 Sep '09

11 Sep '09

Typo in Configuring Loggers documentation ----------------------------------------- Key: LBSITE-33 URL: http://jira.qos.ch/browse/LBSITE-33 Project: logback-site Issue Type: Bug Components: Documentation Affects Versions: 0.9.17 Reporter: Mark Vedder Assignee: Logback dev list Priority: Minor In the "Configuring Loggers, or the <logger> element" section of the configuration chapter (http://logback.qos.ch/manual/configuration.html) the attribute name additivity is incorrectly shown as "aditivity" in the second sentence of the first paragraph: "...and an optional aditivity attribute, which admits the values true or false." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Commented: (LBCORE-26) TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file.
by steveneo (JIRA) 09 Sep '09

09 Sep '09

[ http://jira.qos.ch/browse/LBCORE-26?page=com.atlassian.jira.plugin.system.i… ] steveneo commented on LBCORE-26: -------------------------------- This bug still exists in 0.9.17. I test Pavel config, it is not work as well. My config like this: <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${USER_HOME}/log/qas-batch.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-4relative[%d{dd MMM yy HH:mm:ss}][%thread] %-5level %logger{35} - %msg%n</Pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${USER_HOME}/log/qas-batch-%d{yyyy-MM-dd}.log</FileNamePattern> </rollingPolicy> </appender> > TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file. > ---------------------------------------------------------------------------------------- > > Key: LBCORE-26 > URL: http://jira.qos.ch/browse/LBCORE-26 > Project: logback-core > Issue Type: Bug > Components: Rolling > Affects Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Tsutomu YANO > Assignee: Logback dev list > Priority: Critical > Fix For: 0.9.12 > > > If you use TimeBasedRollingPolicy to rollover a log file and no log wasn't wrote into the log beyond the timing of rollover, and if you restart your application, the log file doesn't roll, then new log will be appended into old log file. > EVIDENCE: > 1. in logback.xml, set your FileNamePattern like 'log.%d{yyyy-MM-dd_HH-mm}.log'. > 2. Simply do a kind of thing, which will make some logs into your log file. > 3. Wait for some minutes. > 4. restart your application. > 5. do a kind of thing, which will make some logs into your log file. > the FileNamePattern is 'log.%d{yyyy-MM-dd_HH-mm}.log', so the log file will be roll every minutes. On case 5 of above example, the log file should be roll over, because some minutes already have passed after last logs wrote into the log file. But the file didn't be roll overed. > THE CAUSE: > In start() method of TimeBasedRollingPolicy, you initialize a variable 'lastCheck' to System.currentTimeStamp(). So if you restart your application, the last check time will be set to just NOW. > you should initialize the variable to a last modified time of a current log file. > See below source code. from '//modified by Tsutomu YANO' to '//until here'. > SOURCE: > public void start() { > // set the LR for our utility object > util.setContext(this.context); > compress.setContext(this.context); > // find out period from the filename pattern > if (fileNamePatternStr != null) { > fileNamePattern = new FileNamePattern(fileNamePatternStr, this.context); > determineCompressionMode(); > } else { > addWarn(FNP_NOT_SET); > addWarn(SEE_FNP_NOT_SET); > throw new IllegalStateException(FNP_NOT_SET + SEE_FNP_NOT_SET); > } > DateTokenConverter dtc = fileNamePattern.getDateTokenConverter(); > if (dtc == null) { > throw new IllegalStateException("FileNamePattern [" + fileNamePattern.getPattern() + "] does not contain a valid DateToken"); > } > int len = fileNamePatternStr.length(); > switch (compressionMode) { > case Compress.GZ: > activeFileNamePattern = new FileNamePattern(fileNamePatternStr.substring(0, len - 3), this.context); > break; > case Compress.ZIP: > activeFileNamePattern = new FileNamePattern(fileNamePatternStr.substring(0, len - 4), this.context); > break; > case Compress.NONE: > activeFileNamePattern = fileNamePattern; > } > addInfo("Will use the pattern " + activeFileNamePattern + " for the active file"); > rc = new RollingCalendar(); > rc.init(dtc.getDatePattern()); > addInfo("The date pattern is '" + dtc.getDatePattern() + "' from file name pattern '" + fileNamePattern.getPattern() + "'."); > rc.printPeriodicity(this); > > //modified by Tsutomu YANO > //if a current log file exists, initialize a 'lastCheck' variable to the > //last modified date of the file. > File currentFile = new File(getParentFileName()); > if(currentFile.exists() && currentFile.canRead()) { > lastCheck.setTime(currentFile.lastModified()); > } else { > // currentTime = System.currentTimeMillis(); > lastCheck.setTime(getCurrentTime()); > } > //until here > > nextCheck = rc.getNextCheckMillis(lastCheck); > // Date nc = new Date(); > // nc.setTime(nextCheck); > } -- 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

Re: [logback-dev] Logback response. [logback-user] same layout - different results
by Ralph Goers 07 Sep '09

07 Sep '09

On Sep 7, 2009, at 12:27 PM, Rob Lister wrote: > Hi Ralph, > > Thanks for taking a look at this. First time poster - do I respond > to you or logback-user(a)qos.ch ? In general, when working with open source always respond to the mailing list. The mailing lists are archived and are searchable via google, etc. so others get the benefits to the answers to your questions. > > I just realised that some of my text was moved to the end of my name > so I didn't show the full appender; > > Should have been....... > > <param name="LayoutParam1" value="%-5p %x - %m%n"/> > I'm struggling with this as it works fine on our internal system, > but I'm not allowed to test it on our clients site (in Italy) so I > can't reproduce anywhere. What diagnostic info would I need to try > and put this to bed? First, you would want to get a copy of the original log file and send it along without touching it so anyone viewing it can be sure they are seeing the original data. Zip it up and then transfer it in binary so you are sure that the data isn't being touched. Next, you might actually have to look at the code that is generating the log record in question. It may be that variables are being replaced and for some reason those variables are the source of the problem. Also, find out what code page the host system is set to and then see if you can configure your system that way. That can get tricky as your keyboard won't have the correct characters, but you should be fine for Italian since so many of the Latin 1 characters are common. > > I'm a zOS sysprog so have vitually no Unix/log4j/java. It's all a > bit of a culture shock at the moment. > That isn't a problem. I started out as a computer operator on IBM mainframes and was a CICS systems programmer for a few years (back in the dark ages when IBM gave you the source code). I worked at Candle Corp for 17 years working on performance monitoring products for IBM systems (MVS - z/OS, VM, AS/400) and the last several years we were doing all our work on Unix System Services so we could have a common build system across all the various operating systems we supported. I haven't worked on a mainframe since 2001 though and switched from C/C+ + to Java at the same time, but I'm not sure much has changed. Ralph

1 0

Unit test hangs.
by Ralph Goers 07 Sep '09

07 Sep '09

While testing my changes to logback I ran into a bit of a problem with one of the unit tests. ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest hangs every time i run it. I even downloaded from your repository and tried it with the same results. This is on my MacBook Pro. Output from jstack. 2009-09-06 23:16:23 Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.1-b02-90 mixed mode): "Attach Listener" daemon prio=9 tid=0x000000010217e800 nid=0x1148d2000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "SocketAcceptorIoProcessor-2.0" prio=5 tid=0x0000000102c3e800 nid=0x114cda000 runnable [0x0000000114cd9000] 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 <0x0000000106cbd098> (a sun.nio.ch.Util$1) - locked <0x0000000106cbd080> (a java.util.Collections$UnmodifiableSet) - locked <0x0000000106cbcd20> (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=0x0000000102ad9800 nid=0x1146d6000 runnable [0x00000001146d5000] 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 <0x000000010897a298> (a sun.nio.ch.Util$1) - locked <0x000000010897a2b0> (a java.util.Collections$UnmodifiableSet) - locked <0x00000001082b1cc0> (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 @3d015a9e" daemon prio=5 tid=0x0000000102be0000 nid=0x114bd7000 in Object.wait() [0x0000000114bd6000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000001077ffd18> (a org.hsqldb.lib.HsqlTimer) at org.hsqldb.lib.HsqlTimer.nextTask(Unknown Source) - locked <0x00000001077ffd18> (a org.hsqldb.lib.HsqlTimer) at org.hsqldb.lib.HsqlTimer$TaskRunner.run(Unknown Source) at java.lang.Thread.run(Thread.java:637) "Low Memory Detector" daemon prio=5 tid=0x0000000102025800 nid=0x114290000 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "CompilerThread1" daemon prio=9 tid=0x000000010288f000 nid=0x11418d000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "CompilerThread0" daemon prio=9 tid=0x0000000102025000 nid=0x11408a000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" daemon prio=9 tid=0x0000000102024000 nid=0x113f87000 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Surrogate Locker Thread (CMS)" daemon prio=5 tid=0x0000000102023800 nid=0x113e84000 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Finalizer" daemon prio=8 tid=0x0000000102885800 nid=0x113b03000 in Object.wait() [0x0000000113b02000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000001076f0848> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118) - locked <0x00000001076f0848> (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=0x0000000102016800 nid=0x113a00000 in Object.wait() [0x00000001139ff000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000001076f7f50> (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 <0x00000001076f7f50> (a java.lang.ref.Reference$Lock) "main" prio=5 tid=0x0000000102800800 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 <0x0000000106c839c0> (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 <0x0000000106c800c0> (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:279) at ch.qos.logback.core.net.SMTPAppenderBase.append (SMTPAppenderBase.java:150) at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:87) - locked <0x0000000107a67dc0> (a ch.qos.logback.classic.net.SMTPAppender) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders (AppenderAttachableImpl.java:60) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:271) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:258) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend (Logger.java:440) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java: 394) at ch.qos.logback.classic.Logger.error(Logger.java:557) at ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest.htmlLong (SMTPAppender_SubethaSMTPTest.java:182) 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=0x0000000102884000 nid=0x1138fd000 runnable "Gang worker#0 (Parallel GC Threads)" prio=9 tid=0x0000000102802000 nid=0x106102000 runnable "Gang worker#1 (Parallel GC Threads)" prio=9 tid=0x0000000102802800 nid=0x106205000 runnable "Concurrent Mark-Sweep GC Thread" prio=9 tid=0x0000000102842000 nid=0x11359f000 runnable "VM Periodic Task Thread" prio=10 tid=0x0000000102026800 nid=0x114393000 waiting on condition "Exception Catcher Thread" prio=10 tid=0x0000000102801800 nid=0x101701000 runnable JNI global references: 701 Console output: Running ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest TEST 23:53:02.564 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: AUTH TEST 23:53:02.564 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: DATA TEST 23:53:02.564 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: EHLO TEST 23:53:02.564 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: HELO TEST 23:53:02.564 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: HELP TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: MAIL TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: NOOP TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: QUIT TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: RCPT TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: RSET TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: STARTTLS TEST 23:53:02.565 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: VRFY TEST 23:53:02.659 [SocketAcceptorIoProcessor-0.0] DEBUG o.s.smtp.server.ConnectionHandler - Active connections = 1 TEST 23:53:02.661 [SocketAcceptorIoProcessor-0.0] DEBUG o.s.smtp.server.ConnectionHandler - SMTP connection count: 1 TEST 23:53:02.663 [SocketAcceptorIoProcessor-0.0] DEBUG o.s.smtp.server.ConnectionHandler - S: 220 192.168.10.130 ESMTP SubEthaSMTP TEST 23:53:02.672 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.673 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.675 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.676 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.679 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.679 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: EHLO rgoerss-macbook-pro.local TEST 23:53:02.680 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250-192.168.10.130 250-8BITMIME 250-STARTTLS 250 Ok TEST 23:53:02.680 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.680 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.680 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.681 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.681 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: MAIL FROM:<user(a)host.dom> TEST 23:53:02.681 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:02.681 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.681 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.682 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.682 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.682 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: RCPT TO:<noreply(a)qos.ch> TEST 23:53:02.683 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:02.683 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.683 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.684 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.684 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.684 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: DATA TEST 23:53:02.684 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 354 End data with <CR><LF>.<CR><LF> TEST 23:53:02.684 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.684 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.685 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.690 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.692 [SubEthaSMTP Thread 1] DEBUG org.subethamail.wiser.Wiser - Delivering new message ... TEST 23:53:02.704 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:02.705 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.705 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.705 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.706 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.706 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: QUIT TEST 23:53:02.706 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 221 Bye TEST 23:53:02.707 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 TEST 23:53:02.710 [SocketAcceptorIoProcessor-0.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61067 TEST 23:53:02.714 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - Active connections = 0 TEST 23:53:02.715 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61067 [HEADER 190 [main] DEBUG test ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest - hello 191 [main] ERROR test ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest - en error java.lang.Exception: an exception at ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest.smoke (SMTPAppender_SubethaSMTPTest.java:122) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na: 1.6.0_15] at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) [na:1.6.0_15] at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) [na:1.6.0_15] at java.lang.reflect.Method.invoke(Method.java:597) [na:1.6.0_15] at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) [junit-4.4.jar:na] at org.junit.internal.runners.MethodRoadie.runTestMethod (MethodRoadie.java:98) [junit-4.4.jar:na] at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java: 79) [junit-4.4.jar:na] at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters (MethodRoadie.java:87) [junit-4.4.jar:na] at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java: 77) [junit-4.4.jar:na] at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) [junit-4.4.jar:na] at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod (JUnit4ClassRunner.java:88) [junit-4.4.jar:na] at org.junit.internal.runners.JUnit4ClassRunner.runMethods (JUnit4ClassRunner.java:51) [junit-4.4.jar:na] at org.junit.internal.runners.JUnit4ClassRunner$1.run (JUnit4ClassRunner.java:44) [junit-4.4.jar:na] at org.junit.internal.runners.ClassRoadie.runUnprotected (ClassRoadie.java:27) [junit-4.4.jar:na] at org.junit.internal.runners.ClassRoadie.runProtected (ClassRoadie.java:37) [junit-4.4.jar:na] at org.junit.internal.runners.JUnit4ClassRunner.run (JUnit4ClassRunner.java:42) [junit-4.4.jar:na] at org.apache.maven.surefire.junit4.JUnit4TestSet.execute (JUnit4TestSet.java:62) [surefire-junit4-2.4.2.jar:2.4.2] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet (AbstractDirectoryTestSuite.java:140) [surefire-api-2.4.2.jar:2.1] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute (AbstractDirectoryTestSuite.java:127) [surefire-api-2.4.2.jar:2.1] at org.apache.maven.surefire.Surefire.run(Surefire.java:177) [surefire-api-2.4.2.jar:2.1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na: 1.6.0_15] at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) [na:1.6.0_15] at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) [na:1.6.0_15] at java.lang.reflect.Method.invoke(Method.java:597) [na:1.6.0_15] at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess (SurefireBooter.java:338) [surefire-booter-2.4.2.jar:na] at org.apache.maven.surefire.booter.SurefireBooter.main (SurefireBooter.java:997) [surefire-booter-2.4.2.jar:na] FOOTER TEST 23:53:02.726 [main] INFO o.subethamail.smtp.server.SMTPServer - SMTP Server socket shut down. TEST 23:53:02.743 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: AUTH TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: DATA TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: EHLO TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: HELO TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: HELP TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: MAIL TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: NOOP TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: QUIT TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: RCPT TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: RSET TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: STARTTLS TEST 23:53:02.745 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: VRFY TEST 23:53:02.763 [SocketAcceptorIoProcessor-1.0] DEBUG o.s.smtp.server.ConnectionHandler - Active connections = 1 TEST 23:53:02.763 [SocketAcceptorIoProcessor-1.0] DEBUG o.s.smtp.server.ConnectionHandler - SMTP connection count: 1 TEST 23:53:02.763 [SocketAcceptorIoProcessor-1.0] DEBUG o.s.smtp.server.ConnectionHandler - S: 220 192.168.10.130 ESMTP SubEthaSMTP TEST 23:53:02.774 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.778 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: EHLO rgoerss-macbook-pro.local TEST 23:53:02.778 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250-192.168.10.130 250-8BITMIME 250-STARTTLS 250 Ok TEST 23:53:02.778 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.779 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.779 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.779 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.780 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: MAIL FROM:<user(a)host.dom> TEST 23:53:02.780 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:02.780 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.780 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.780 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.780 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.783 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: RCPT TO:<noreply(a)qos.ch> TEST 23:53:02.784 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:02.784 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.784 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.784 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.784 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.784 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: DATA TEST 23:53:02.784 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 354 End data with <CR><LF>.<CR><LF> TEST 23:53:02.785 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.785 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.785 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.796 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.796 [SubEthaSMTP Thread 1] DEBUG org.subethamail.wiser.Wiser - Delivering new message ... TEST 23:53:02.796 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:02.796 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.798 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.806 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.807 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.807 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: QUIT TEST 23:53:02.807 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 221 Bye TEST 23:53:02.808 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.808 [SocketAcceptorIoProcessor-1.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61068 TEST 23:53:02.809 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - Active connections = 0 TEST 23:53:02.810 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61068 TEST 23:53:02.918 [main] INFO o.subethamail.smtp.server.SMTPServer - SMTP Server socket shut down. TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: AUTH TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: DATA TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: EHLO TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: HELO TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: HELP TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: MAIL TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: NOOP TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: QUIT TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: RCPT TEST 23:53:02.923 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: RSET TEST 23:53:02.924 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: STARTTLS TEST 23:53:02.924 [main] DEBUG o.s.smtp.server.CommandHandler - Added command: VRFY TEST 23:53:03.073 [SocketAcceptorIoProcessor-2.0] DEBUG o.s.smtp.server.ConnectionHandler - Active connections = 1 TEST 23:53:03.073 [SocketAcceptorIoProcessor-2.0] DEBUG o.s.smtp.server.ConnectionHandler - SMTP connection count: 1 TEST 23:53:03.074 [SocketAcceptorIoProcessor-2.0] DEBUG o.s.smtp.server.ConnectionHandler - S: 220 192.168.10.130 ESMTP SubEthaSMTP TEST 23:53:03.074 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.074 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.074 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.075 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.075 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.076 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: EHLO rgoerss-macbook-pro.local TEST 23:53:03.076 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250-192.168.10.130 250-8BITMIME 250-STARTTLS 250 Ok TEST 23:53:03.076 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.077 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.077 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.077 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.077 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: MAIL FROM:<user(a)host.dom> TEST 23:53:03.077 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:03.077 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.078 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.078 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.078 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.078 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: RCPT TO:<noreply(a)qos.ch> TEST 23:53:03.078 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 250 Ok TEST 23:53:03.078 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.079 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.079 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - C: DATA TEST 23:53:03.079 [SubEthaSMTP Thread 1] DEBUG o.s.smtp.server.ConnectionHandler - S: 354 End data with <CR><LF>.<CR><LF> TEST 23:53:03.080 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 TEST 23:53:03.080 [SocketAcceptorIoProcessor-2.0] DEBUG o.a.m.filter.executor.ExecutorFilter - Launching thread for / 127.0.0.1:61069 TEST 23:53:03.080 [SubEthaSMTP Thread 1] DEBUG o.a.m.filter.executor.ExecutorFilter - Exiting since queue is empty for /127.0.0.1:61069 ^CDestroying 1 processes Destroying process.. Destroyed 1 processes

1 0

Lost internet connectivity
by Ceki Gulcu 05 Sep '09

05 Sep '09

Hello all, There was a wiring problem in our building (qos.ch) where cal10n, logback and slf4j projects are hosted. As consequence, our various web-sites were unreachable for about 12 hours. The issue was fixed just a few minutes ago with the help of our internet provider. We are currently working on duplicating parts of our infrastructure so that such connectivity problems if they re-occur, will have much less of an impact. My apologies for the inconvenience. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

branch, master, updated. 0490aa2ba37613c66519aa4087901444be1939b8
by git-noreply＠pixie.qos.ch 02 Sep '09

02 Sep '09

The branch, master has been updated via 0490aa2ba37613c66519aa4087901444be1939b8 (commit) from 0a9c28e40bfc48a91a097776c970cb421b37dd10 (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=0490aa2ba37613c66519aa40… http://github.com/ceki/logback/commit/0490aa2ba37613c66519aa4087901444be193… commit 0490aa2ba37613c66519aa4087901444be1939b8 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Sep 2 12:53:57 2009 +0200 - mindor editing in support.html diff --git a/logback-site/src/site/pages/images/qoslogo.gif b/logback-site/src/site/pages/images/qoslogo.gif index 1accb13..2fc95ca 100644 Binary files a/logback-site/src/site/pages/images/qoslogo.gif and b/logback-site/src/site/pages/images/qoslogo.gif differ diff --git a/logback-site/src/site/pages/support.html b/logback-site/src/site/pages/support.html index 2189219..e3b5942 100644 --- a/logback-site/src/site/pages/support.html +++ b/logback-site/src/site/pages/support.html @@ -19,28 +19,25 @@ </div> <div id="content"> - <h2>Professional Logback Support</h2> + <h2>Professional Support</h2> - <p>Although the quality of support in the various public logback - mailing lists is quite good, these are operated on a best-effort - basis. If you require authoritative responses and guaranteed - response times, then you should consider our professional support - package. + <p>Although the quality of support in the various open source + project mailing lists is quite good, these are operated on a + best-effort basis. If you require authoritative responses and + guaranteed response times, then you should consider our + professional support package. </p> - <p>As the founders and current maintainers of the logback project, - we can offer you the highest quality of support. Opting for our - professional logback support service is a great way to leverage - the expertise of logback developers. + <p>As the founders and/or current maintainers of the slf4j, log4j, + logback and <a href="http://cal10n.qos.ch/">cal10n</a> projects, + we can offer you timely and competent support. Choosing our + professional support service is a good way to leverage our + expertise. Moreovoer, if you require custom development we are + likely to be of help. </p> - <p>Moreovoer, if your project requires custom appenders or logback - extensions, we are likely to be of help. - </p> - - <p>For more information about Professional Logback Support do not - hesitate to contact us. We will be happy to discuss your - logging-related questions.</p> + <p>For more information about Professional Support do not hesitate + to contact us. We will be happy to discuss your needs.</p> <table> <tr> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/images/qoslogo.gif | Bin 3300 -> 1633 bytes logback-site/src/site/pages/support.html | 31 ++++++++++------------- 2 files changed, 14 insertions(+), 17 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-152) XMLLayout thread safety
by Darryl Smith (JIRA) 29 Aug '09

29 Aug '09

XMLLayout thread safety ----------------------- Key: LBCLASSIC-152 URL: http://jira.qos.ch/browse/LBCLASSIC-152 Project: logback-classic Issue Type: Bug Components: layout Affects Versions: 0.917 Reporter: Darryl Smith Assignee: Logback dev list XMLLayout assumes it is being called from a synchronized appender and uses shared StringBuilder buffer for creating the layout. Changes in http://jira.qos.ch/browse/LBCLASSIC-135 break that assumption -- 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