- logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCORE-171) Can't use logback on GAE SDK 1.3.7 when configured with logback.xml
by Maxim Veksler (JIRA) 10 Nov '12

10 Nov '12

Can't use logback on GAE SDK 1.3.7 when configured with logback.xml ------------------------------------------------------------------- Key: LBCORE-171 URL: http://jira.qos.ch/browse/LBCORE-171 Project: logback-core Issue Type: Bug Affects Versions: 0.9.24 Environment: GAE/J 1.3.7 Reporter: Maxim Veksler Assignee: Logback dev list Trying to initialize logback with custom configuration file (logback.xml) running on GAE platform throws the following exception Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.NoClassDefFoundError: java.net.InetAddress is a restricted class. Please see the Google App Engine developer's guide for more details. at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51) at ch.qos.logback.core.util.ContextUtil.getLocalHostName(ContextUtil.java:30) at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:39) at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:47) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:273) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:145) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:127) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:40) at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) ...... This happens because ch.qos.logback.core.util.ContextUtil.java contains are reference to a java.net.InetAddress which is a restricted class on Google AppEngine Platform SDK 1.3.7: static String getLocalHostName() throws UnknownHostException { InetAddress localhost = InetAddress.getLocalHost(); return localhost.getHostName(); } I should note that BasicConfigurator is working and is able to configure the logback subsystem. A couple of resolutions I can think of: 1. Don't export this parameter by default, instead let the user choose if to define it or not in the logback.xml configuration file. 2. Create a "GAEConfigurator" which will use default for the limited GAE environment. 2. Provide a custom build for GAE platform, where this parameter will be taken from http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api… or not be defined at all. 4. Provide some method to override / use a different implementation of ContextUtil, one which will be suitable for GAE. -- 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 2

[JIRA] (LOGBACK-760) Failed to instantiate LoggerContext
by Jaroslav Holubec (JIRA) 10 Nov '12

10 Nov '12

2 1

[JIRA] (LOGBACK-725) Logging System fails silently when config filename has an unsupported extension
by Ryan Scheidter (JIRA) 09 Nov '12

09 Nov '12

3 3

[JIRA] Created: (LBCORE-209) Print configuration errors to stderr
by atomicknight (JIRA) 09 Nov '12

09 Nov '12

Print configuration errors to stderr ------------------------------------ Key: LBCORE-209 URL: http://jira.qos.ch/browse/LBCORE-209 Project: logback-core Issue Type: Improvement Components: Other Affects Versions: 0.9.28 Reporter: atomicknight Assignee: Logback dev list In org.slf4j.impl.StaticLoggerBinder#init(), any detected configuration errors are passed to StatusPrinter to be printed. However, the default PrintStream used by StatusPrinter is stdout, which can interfere with the output of command-line based Java programs that are used in the same fashion as applications such as ls or grep. Would it be possible to modify this behavior such that configuration errors are printed to stderr instead? A potential solution would be to overload StatusPrinter#printInCaseofErrorsOrWarning and StatusPrinter#printIfErrorsOccurred with versions that also take a PrintStream as an argument - this would allow classes like StaticLoggerBinder to specify the appropriate output stream without overriding the global state in StatusPrinter. Alternatively, an additional setting in the XML configuration might work just as well. -- 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 11

[qos-ch/logback] 3959ff: ongoing work
by Ceki Gulcu 08 Nov '12

08 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 3959ffb81a15943a1b8647b2e463a74e7a55dcef https://github.com/qos-ch/logback/commit/3959ffb81a15943a1b8647b2e463a74e7a… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-08 (Thu, 08 Nov 2012) Changed paths: M logback-site/src/site/pages/manual/configuration.html M logback-site/src/site/pages/manual/layouts.html M logback-site/src/site/pages/news.html Log Message: ----------- ongoing work

1 0

[JIRA] (LOGBACK-751) Configuration file specified by "logback.configurationFile" system property isn't applied when it doesn't have a .xml filename extension
by Libor Jelinek (JIRA) 08 Nov '12

08 Nov '12

3 3

[qos-ch/logback] 8eb405: update docs, cosmetic changes
by Ceki Gulcu 08 Nov '12

08 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 8eb405e6c230987dc47815c72b175a04c275eb75 https://github.com/qos-ch/logback/commit/8eb405e6c230987dc47815c72b175a04c2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-08 (Thu, 08 Nov 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/joran/action/ConfigurationAction.java M logback-classic/src/main/java/org/slf4j/impl/StaticLoggerBinder.java M logback-classic/src/test/java/org/slf4j/impl/InitializationOutputTest.java M logback-site/src/site/pages/manual/configuration.html Log Message: ----------- update docs, cosmetic changes

1 0

[JIRA] (LOGBACK-767) OnConsoleStatusListener initialized with system property (logback.statusListenerClass) is never started
by Adam Sokowicz (JIRA) 08 Nov '12

08 Nov '12

2 4

[qos-ch/logback] 3c3182: LOGBACK-767 setting context
by Ceki Gulcu 08 Nov '12

08 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 3c318239b6ba8f2db3bd67e008014921d520227e https://github.com/qos-ch/logback/commit/3c318239b6ba8f2db3bd67e008014921d5… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-08 (Thu, 08 Nov 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/util/StatusListenerConfigHelper.java M logback-core/src/main/java/ch/qos/logback/core/status/OnPrintStreamStatusListenerBase.java Log Message: ----------- LOGBACK-767 setting context

1 0

[qos-ch/logback] ecfb80: ongoing work on logback-292
by Ceki Gulcu 07 Nov '12

07 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: ecfb80be281f3682972052fbd6217092b5ae62cd https://github.com/qos-ch/logback/commit/ecfb80be281f3682972052fbd6217092b5… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-07 (Wed, 07 Nov 2012) Changed paths: A logback-classic/src/test/input/issue/logback292.xml Log Message: ----------- ongoing work on logback-292

1 0