August 2012 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-743) joranconfigurator fails if used in applet
by Gerhard Presser (JIRA) 11 Oct '12

11 Oct '12

1 1

[JIRA] Created: (LBCORE-228) Syslog messages over 64K are discarded
by Pasi Eronen (JIRA) 25 Sep '12

25 Sep '12

Syslog messages over 64K are discarded -------------------------------------- Key: LBCORE-228 URL: http://jira.qos.ch/browse/LBCORE-228 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.30 Reporter: Pasi Eronen Assignee: Logback dev list SyslogAppenderBase truncates very long messages to 256k, which is not very useful limit, since SyslogOutputStream supports only UDP, which has maximum message size of 64k. Messages over 64k result in "java.io.IOException: Message too long" (from DatagramSocket.send, called from SyslogOutputStream.flush), but this exception is visible only in logger context status... Proposed fix: truncate long messages instead of discarding them. More specifically, change MSG_SIZE_LIMIT in SyslogAppenderBase to 65000. -- 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: (LBCLASSIC-319) SyslogAppender prints %PARSER_ERROR[nopexXXX] when suffixPattern doesn't start with [
by Markus Binsteiner (JIRA) 25 Sep '12

25 Sep '12

SyslogAppender prints %PARSER_ERROR[nopexXXX] when suffixPattern doesn't start with [ ------------------------------------------------------------------------------------- Key: LBCLASSIC-319 URL: http://jira.qos.ch/browse/LBCLASSIC-319 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.30, 1.0.0 Reporter: Markus Binsteiner Assignee: Logback dev list Priority: Minor When I use the SyslogAppender and specify a suffixPattern that starts with a whitespace or other character that is not [ logback seems to just append the string (until the first occurence of certain characters, e.g -) to the internal "%nopex" string. Subsequently it fails to parse the %nopexXXX string and prints something like: Jan 12 15:54:14 think %PARSER_ERROR[nopexXXX] [main] LogTest DEBUG FROM JAVA... to syslog. Had a look in the sourcecode, but couldn't figure out where it goes wrong, but I could confirm that if I add a whitespace to the string in this line String prefixPattern = "%syslogStart{" + facilityStr + "}%nopex "; there is no PARSER_ERROR. An additional whitespace in the logmessage though (I can live with that though). I need to be able to specify a string that doesn't start with [ though for some crazy reason (almost funny -- every other character would have been ok as far as I could figure out...). Any chance that could be looked into and included in one of the next releases? Thanks in advance... -- 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-248) Logback Context is not thread safe, throws java.util.ConcurrentModificationException
by Svetla Arnaudova (JIRA) 22 Sep '12

22 Sep '12

Logback Context is not thread safe, throws java.util.ConcurrentModificationException ------------------------------------------------------------------------------------- Key: LBCORE-248 URL: http://jira.qos.ch/browse/LBCORE-248 Project: logback-core Issue Type: Bug Affects Versions: 1.0.0 Environment: Windows 7 OS, Java 1.6 build 1.6.0_27-b07, Tomcat 7 Reporter: Svetla Arnaudova Assignee: Logback dev list We see the following exception in Status messages for LoggerContext (see attached pic lbClassicStatus.jpg) java.util.ConcurrentModificationException at java.util.Hashtable$Enumerator.next(Hashtable.java:1031) at ch.qos.logback.classic.LoggerContext.syncRemoteView(LoggerContext.java:93) at ch.qos.logback.classic.LoggerContext.putProperty(LoggerContext.java:101) at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:42) at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:48) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:276) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:148) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:130) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:147) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:133) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:55) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at com.excilys.ebi.utils.spring.log.logback.LogbackConfigurer.initLogging(LogbackConfigurer.java:90) at com.excilys.ebi.utils.spring.log.logback.web.LogbackWebConfigurer.initLogging(LogbackWebConfigurer.java:92) at com.excilys.ebi.utils.spring.log.logback.web.LogbackConfigListener.contextInitialized(LogbackConfigListener.java:43) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4723) at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226) at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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:662) Our web application set default configuration logback.xml file in the class path so that logback will use it to configure itself during initialization. It is slightly different (only set info level) from the default basic configuration, used in case there is no such file (see attached logback.xml). The real logback.xml configuration file is outside of the web application (attached as logback-conf.xml) and we reconfigure logapp to use it with spring integration lib https://github.com/excilys/spring-log Not sure that the rest of the description will be helpful to troubleshoot the problem, but this is how we reproduce it: This is the example code: <context-param> <param-name>logbackConfigLocation</param-name> <param-value>file:${basedir}/conf/logback.xml</param-value> </context-param> <listener> <listener-class>com.excilys.ebi.utils.spring.log.logback.web.LogbackConfigListener</listener-class> </listener> After spring is loaded LogbackConfigListener class will initialize logback from the given location and reset the logger context. Code snip from LogbackConfigListener init logging below: public static void initLogging(String location) throws FileNotFoundException, JoranException { String resolvedLocation = SystemPropertyUtils.resolvePlaceholders(location); URL url = ResourceUtils.getURL(resolvedLocation); ContextSelector selector = ContextSelectorStaticBinder.getSingleton().getContextSelector(); LoggerContext loggerContext = selector.getLoggerContext(); // in the current version logback automatically configures at startup // the context, so we have to reset it loggerContext.reset(); ContextInitializer contextInitializer = new ContextInitializer(loggerContext); contextInitializer.configureByResource(url); // reset JUL // don't forget to configure the LevelChangePropagator contextListener // in the config file!!! SLF4JBridgeHandler.install(); } We sometimes receive concurrency modification exception from the logback core code. We never observe this issue if we remove default logback file from the class path as initial configuration. To prevent this exception we also delay logback configuration loading. Thank you, Svetla -- 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 4

[JIRA] (LOGBACK-718) Support Eclipse buddy policy for loading logback.xml
by Ceki Gulcu (JIRA) 19 Sep '12

19 Sep '12

7 10

[JIRA] (CONSPLUG-34) modification in the logger tree incorrectly clears main storage buffer
by Ceki Gulcu (JIRA) 04 Sep '12

04 Sep '12

1 2

[JIRA] (CONSPLUG-35) Add Save/Load of Logback-Beagle logging preferences.
by Larry Smith (JIRA) 04 Sep '12

04 Sep '12

2 6

[qos-ch/logback] 2c04fd: added findbugs to the build
by Ceki Gulcu 31 Aug '12

31 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 2c04fd4e467e8e37d75ceb5314e19a170d6b8da1 https://github.com/qos-ch/logback/commit/2c04fd4e467e8e37d75ceb5314e19a170d… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-31 (Fri, 31 Aug 2012) Changed paths: A findbugs-exclude.xml M logback-access/src/main/java/ch/qos/logback/access/pattern/EnsureLineSeparation.java M logback-core/pom.xml M logback-core/src/main/java/ch/qos/logback/core/pattern/FormatInfo.java M logback-core/src/main/java/ch/qos/logback/core/pattern/parser/CompositeNode.java M logback-core/src/main/java/ch/qos/logback/core/pattern/parser/FormattingNode.java M logback-core/src/main/java/ch/qos/logback/core/pattern/parser/Node.java M logback-core/src/main/java/ch/qos/logback/core/pattern/parser/SimpleKeywordNode.java M pom.xml Log Message: ----------- added findbugs to the build

1 0

[qos-ch/logback] abff3a: adding findbugs to the build
by Ceki Gulcu 31 Aug '12

31 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: abff3abe6f36bc5cc0ff1da49622447c9b5bcda1 https://github.com/qos-ch/logback/commit/abff3abe6f36bc5cc0ff1da49622447c9b… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-31 (Fri, 31 Aug 2012) Changed paths: M logback-access/src/main/java/ch/qos/logback/access/PatternLayout.java M logback-classic/src/main/java/ch/qos/logback/classic/db/DBHelper.java M logback-classic/src/main/java/ch/qos/logback/classic/joran/action/InsertFromJNDIAction.java M logback-classic/src/main/java/ch/qos/logback/classic/spi/CallerData.java M logback-classic/src/main/java/ch/qos/logback/classic/util/ContextInitializer.java M logback-core/pom.xml M logback-core/src/main/java/ch/qos/logback/core/CoreConstants.java M logback-core/src/main/java/ch/qos/logback/core/encoder/ObjectStreamEncoder.java M logback-core/src/main/java/ch/qos/logback/core/joran/conditional/IfAction.java M logback-core/src/main/java/ch/qos/logback/core/rolling/FixedWindowRollingPolicy.java M logback-core/src/main/java/ch/qos/logback/core/subst/Token.java M logback-core/src/main/java/ch/qos/logback/core/util/Loader.java M logback-examples/src/main/java/chapters/onJoran/calculator/ComputationAction1.java M logback-examples/src/main/java/chapters/onJoran/calculator/ComputationAction2.java M logback-examples/src/main/java/chapters/onJoran/calculator/LiteralAction.java M logback-site/src/site/pages/beagle/index.html A logback-site/src/site/resources/beagle/images/font.png M pom.xml Log Message: ----------- adding findbugs to the build

1 0

Release of logback-beagle 1.1.3
by ceki 31 Aug '12

31 Aug '12

Hello all, I am happy to announce the release of logback-beagle 1.1.3, an eclipse plug-in for viewing logs. Compared to release 1.1.2, this release fixes a number of bugs and adds minor new features. - Fixed issues: CONSPLUG-34 modification of logger tree incorrectly clears all buffers - Documentation For more information on logback-beagle please see: http://logback.qos.ch/beagle/ - Installation Logback-beagle requires the Nebula Grid which can be installed from http://download.eclipse.org/technology/nebula/snapshot/ Once Nebula Grid is installed, you can install logback-beagle from http://logback.qos.ch/p2/ - Upgrading If you have already installed a previous version of logback-beagle, invoking Help -> "Check for Updates" in Eclipse should discover this new release of logback-beagle. - Announcement mailing list You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki http://tinyurl.com/proLogback

1 0