July 2016 - logback-user - mailman3.qos.ch

Logback => TLS/SSL => Syslog ?
by Otis Gospodnetić 21 Feb '19

21 Feb '19

Hi, Does Logback support sending logs to Syslog servers via TLS/SSL? I have a feeling Logback doesn't have a SyslogAppender that can send data using TLS. I say that because I don't see a mention of "syslog" on http://logback.qos.ch/manual/usingSSL.html and I see http://jira.qos.ch/browse/LOGBACK-890 that mentions TLSSyslogAppender, but it looks like this never ended up in Logback. I've only found it committed here: https://github.com/balabit/logback/commit/e0d89de2536e0925a6c816a50793f6a74… Could anyone please clarify? Thanks, Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/

2 1

Re: [logback-user] Custom Appender Configuration using generic Properties
by John Page 28 Jul '16

28 Jul '16

Ceki, Thanks for your reply. In your email you wrote: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "The second form would work just fine as long as "thisPropertyName" has a setter." - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I realize each property could be configured by name, but the underlying library is deep and complex. It currently has 49 optional properties. It would require a significant amount of work to add the required setters to the Custom Appender. It would require even more work to maintain the Appender as the underlying library evolves and changes. By providing a "pass-through' Properties configuration, the custom appender will have a long life on Github with less maintenance required. Instead of using the appender documentation, developers can simply refer to the configuration guide provided by the underlying library. The Appender will simply pass the configured properties through to the underlying library. Cheers, John Page

1 0

Custom Appender Configuration using generic Properties
by John Page 28 Jul '16

28 Jul '16

Hi, I have developed a custom appender for logback and would like to configure it with a generic set of Properties that I can pass on to the underlying libraries. Rather than create a Getter and Setter for each property that the underlying library uses, I would like the configuration to read the names and values out of the logback configuration file. Instead of this: <configuration> Thanks, John Page

2 3

startListener ERROR when using Spring logback extension
by Leonid Kagan 28 Jul '16

28 Jul '16

After what looks like all appropriate configurations are performs to use logback with Spring web application a "SEVERE: Error listenerStart" is shown by Tomcat on the application start. Any ideas? The details of environment and configuration are below. Java 7 Tomcat 7 Spring 3.1.4 slf4j 1.7.5 logback-ext-spring 0.1.4 logback.xml: <configuration debug="true"> <appender name="appLogFile" class="ch.qos.logback.ext.spring.DelegatingLogbackAppender"/> <root level="debug"> <appender-ref ref="appLogFile" /> </root> </configuration> web.xml: .... <listener> <listener-class>ch.qos.logback.ext.spring.web.LogbackConfigListener</listener-class> </listener> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> .... spring-app-config.xml: .... <bean class="ch.qos.logback.ext.spring.ApplicationContextHolder"/> <bean id="appLogFile" class="ch.qos.logback.core.FileAppender" init-method="start" destroy-method="stop"> <property name="context" value="#{ T(org.slf4j.LoggerFactory).getILoggerFactory() }"/> <property name="file" value="${catalina.home}/logs/${app.name }.log"/> <property name="encoder"> <bean class="ch.qos.logback.classic.encoder.PatternLayoutEncoder" init-method="start" destroy-method="stop"> <property name="context" value="#{ T(org.slf4j.LoggerFactory).getILoggerFactory() }"/> <property name="pattern" value="%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg%n"/> </bean> </property> </bean> ....

1 0

Fwd: logback start listener invoked twice
by Евгений Бушуев 19 Jul '16

19 Jul '16

Hello Could somebody please explain if it's ok when statusListener.start method is invoked twice? I.e. can it be bug rather than feature? As far as I understand it's getting invoked from LogerFactory.bind method: private final static void bind() { ... Set<URL> staticLoggerBinderPathSet = null; // skip check under android, see also http://jira.qos.ch/browse/SLF4J-328 if (!isAndroid()) { staticLoggerBinderPathSet = findPossibleStaticLoggerBinderPathSet(); reportMultipleBindingAmbiguity(staticLoggerBinderPathSet); } // the next line does the binding StaticLoggerBinder.getSingleton(); <---fist from here INITIALIZATION_STATE = SUCCESSFUL_INITIALIZATION; reportActualBinding(staticLoggerBinderPathSet); replayEvents(); <---then from here ... } The stacktraces: Connected to the target VM, address: 'localhost:7778', transport: 'socket' at my.app.LogListener.start(PECQuartzListener.java:41) at ch.qos.logback.core.joran.action.StatusListenerAction.end(StatusListenerAction.java:65) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:309) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:193) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:179) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:155) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:142) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:103) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:149) <================================= at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:390) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:340) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:361) at my.app.AuthorisationListener.<init>(AuthorisationListener.java:34) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at com.ibm.ws.managedobject.internal.ManagedObjectFactoryImpl.createManagedObject(ManagedObjectFactoryImpl.java:65) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.inject(WebApp.java:1250) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.injectAndPostConstruct(WebApp.java:1416) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.injectAndPostConstruct(WebApp.java:1404) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.loadListener(WebApp.java:813) at com.ibm.ws.webcontainer.webapp.WebApp.loadLifecycleListeners(WebApp.java:2246) at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:1040) at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:6463) at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApp(DynamicVirtualHost.java:446) at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApplication(DynamicVirtualHost.java:441) at com.ibm.ws.webcontainer.osgi.WebContainer.startWebApplication(WebContainer.java:1000) at com.ibm.ws.webcontainer.osgi.WebContainer.startModule(WebContainer.java:824) at com.ibm.ws.app.manager.web.internal.WebModuleHandlerImpl.deployModule(WebModuleHandlerImpl.java:103) at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployModule(DeployedAppInfoBase.java:871) at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployModules(DeployedAppInfoBase.java:831) at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployApp(DeployedAppInfoBase.java:818) at com.ibm.ws.app.manager.ear.internal.EARApplicationHandlerImpl.install(EARApplicationHandlerImpl.java:84) at com.ibm.ws.app.manager.internal.statemachine.StartAction.execute(StartAction.java:141) at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.enterState(ApplicationStateMachineImpl.java:1192) at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.run(ApplicationStateMachineImpl.java:805) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) java.lang.Exception at my.app.LogListener.start(PECQuartzListener.java:41) at ch.qos.logback.core.joran.action.StatusListenerAction.end(StatusListenerAction.java:65) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:309) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:193) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:179) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:155) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:142) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:103) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at ch.qos.logback.classic.selector.ContextJNDISelector.getLoggerContext(ContextJNDISelector.java:108) at org.slf4j.impl.StaticLoggerBinder.getLoggerFactory(StaticLoggerBinder.java:108) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:396) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:340) at org.slf4j.LoggerFactory.replaySingleEvent(LoggerFactory.java:220) at org.slf4j.LoggerFactory.replayEvents(LoggerFactory.java:195) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:152) <================================= at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:390) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:340) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:361) at my.app.AuthorisationListener.<init>(AuthorisationListener.java:34) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at com.ibm.ws.managedobject.internal.ManagedObjectFactoryImpl.createManagedObject(ManagedObjectFactoryImpl.java:65) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.inject(WebApp.java:1250) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.injectAndPostConstruct(WebApp.java:1416) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.injectAndPostConstruct(WebApp.java:1404) at com.ibm.ws.webcontainer.osgi.webapp.WebApp.loadListener(WebApp.java:813) at com.ibm.ws.webcontainer.webapp.WebApp.loadLifecycleListeners(WebApp.java:2246) at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:1040) at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:6463) at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApp(DynamicVirtualHost.java:446) at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApplication(DynamicVirtualHost.java:441) at com.ibm.ws.webcontainer.osgi.WebContainer.startWebApplication(WebContainer.java:1000) at com.ibm.ws.webcontainer.osgi.WebContainer.startModule(WebContainer.java:824) at com.ibm.ws.app.manager.web.internal.WebModuleHandlerImpl.deployModule(WebModuleHandlerImpl.java:103) at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployModule(DeployedAppInfoBase.java:871) at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployModules(DeployedAppInfoBase.java:831) at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployApp(DeployedAppInfoBase.java:818) at com.ibm.ws.app.manager.ear.internal.EARApplicationHandlerImpl.install(EARApplicationHandlerImpl.java:84) at com.ibm.ws.app.manager.internal.statemachine.StartAction.execute(StartAction.java:141) at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.enterState(ApplicationStateMachineImpl.java:1192) at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.run(ApplicationStateMachineImpl.java:805) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) I'm trying to setup logging in an entangled ear app consisting of a bunch of separate war modules using SiftingAppender and JNDIBasedContextDiscriminator deployed to IBM Liberty. Can't reproduce it in simpler configuration. So far I've just removed all modules but one and start still invoked twice (the bp in AuthorisationListener.java:34 is triggered only once). Any help is highly appreciated. logback version is 1.1.7. Best regards, Eugene.

1 0

Using parameter markers and exceptions in non-Logback bindings
by Ti Strga 12 Jul '16

12 Jul '16

There's an entry in the FAQ at http://www.slf4j.org/faq.html#paramException asking how to parameterize a logging statement when also passing an exception. The FAQ explains that the API will automatically figure it out, as long as the last argument passed is the exception and not some other kind of object. (This would be nice to mention in the javadocs if feasible.) My question: the FAQ refers to SLF4J 1.6.0 and "the SLF4J API", but the only place I saw this actually implemented was in logback-classic (the LoggingEvent class in ch.qos.logback.classic.spi, not the LoggingEvent in org.slf4j.event). Are other implementations of the SLF4J API expected to provide the same behavior? Because the wording makes it sound like SLF4J is doing the work on behalf of the implementation, but obviously an interface class can't do that. :-) Am I just misinterpreting the FAQ? thanks, Ti

1 0

Avoid pre-initialization upon the first LoggerFactory.getILoggerFactory();
by Brice Dutheil 08 Jul '16

08 Jul '16

Hi, I would like share a single log configuration for two web-apps that run on the same container. Yet I want each web-app to log in separate files. I tried different approach the best one is actually very close to some solution I later found on the FAQ : http://logback.qos.ch/faq.html#sharedConfiguration LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator jc = new JoranConfigurator(); jc.setContext(loggerContext); loggerContext.reset(); loggerContext.setName(appName); // use ${CONTEXT_NAME} in logback.xml jc.doConfigure(Objects.requireNonNull(source, "Logback configuration is missing")); However for operation reasons we pass the configuration via the system property logback.configurationFile, so what happens is that the first call to LoggerFactory.getILoggerFactory() initialise the LoggerContext and creates files with non initialised variables. As I’m using the context name, the file names have default in their name (this is the default value of the context name), if using variable I get a filename with my-var-name_IS_UNDEFINED. *The question is :* Is there proper way anyway to avoid this pre-initialisation to avoid creating this empty file ? I didn’t found any way to hook in the org.slf4j.LoggerFactory or org.slf4j.impl.StaticLoggerBinder (of logback-classic). — Brice

3 6

Question regarding appenders
by Jose Monreal Bailey 04 Jul '16

04 Jul '16

Good day everyone, Is it possible to have a Console Appender using an AsyncAppender? Does it make sense? I have an logback configuration that seems not to be working, and perhaps it's because of a misconfiguration. Regards, J

2 1