- logback-user - mailman3.qos.ch

Maven Repository cannot resolve logback extensions
by Fritz, Jonathan 25 Feb '14

25 Feb '14

Upon adding the following to my pom.xml: <dependency> <groupId>org.logback-extensions</groupId> <artifactId>logback-ext-loggly</artifactId> <version>version</version> <scope>runtime</scope> </dependency> <dependency> <groupId>ch.qos.logback.contrib</groupId> <artifactId>logback-json-classic</artifactId> <version>version</version> <scope>runtime</scope> </dependency> <dependency> <groupId>ch.qos.logback.contrib</groupId> <artifactId>logback-jackson</artifactId> <version>version</version> <scope>runtime</scope> </dependency> I got this error while running mvn clean install: Failed to execute goal on project webapp: Could not resolve dependencies for project webapp:webapp:war:0.1-SNAPSHOT: The following artifacts could not be resolved: org.logback-extensions:logback-ext-loggly:jar:version, ch.qos.logback.contrib:logback-json-classic:jar:version, ch.qos.logback.contrib:logback-jackson:jar:version: Could not find artifact org.logback-extensions:logback-ext-loggly:jar:version in labs-consol-release (http://labs.consol.de/maven/repository) -> [Help 1] Seems like there might be a problem with the maven repository. Has anybody seen similar issues?

2 4

Repost: ReconfigureOnChangeFilter does not reuse context properties?
by Mike Müller 19 Feb '14

19 Feb '14

Hi At the risk of beeing annoying, I repost my question - in our production environment this is really a problem: -----Original Message----- From: Logback-user [mailto:logback-user-bounces@qos.ch] On Behalf Of Mike Müller Sent: Thursday, January 09, 2014 10:00 AM To: 'logback-user(a)qos.ch' Subject: [logback-user] ReconfigureOnChangeFilter does not reuse context properties? Hi I'm using a config file wich looks like this: <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="60 seconds" > <appender name="cms" class="ch.qos.logback.core.FileAppender"> <file>${pathToLogs}mysign-cms.log</file> <Append>false</Append> <encoder> <pattern>%d %30.30t %-5p %45.45c - %m%n</pattern> </encoder> </appender> <appender name="R" class="ch.qos.logback.core.FileAppender"> <file>${pathToLogs}log.log</file> <Append>false</Append> <encoder> <pattern>%d %30.30t %-5p %45.45c - %m%n</pattern> </encoder> </appender> <logger name="ch.mysign" additivity="false" level="INFO"> <appender-ref ref="cms"/> </logger> <root level="WARN"> <appender-ref ref="R"/> </root> </configuration> The parameter ${pathToLogs} comes from the following code: LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext( context ); context.reset(); context.putProperty( "pathToLog", "my-path-to-the-external-logs" ); configurator.doConfigure("my-logback-config.xml" ); } catch ( JoranException je ) { System.out.println( je.getMessage() ); } If I change the config file, the property "pathToLog" gets lost. Is this the same issue as descibed in [1]? If yes, is it a problem to reuse the context or at least the properties of the old context? [1] http://jira.qos.ch/browse/LOGBACK-592 best regards Mike _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

NPE when extending RollingFileAppender
by Johny Johnson 13 Feb '14

13 Feb '14

Hi, I'm having some trouble getting my custom appender which extends RollingFileAppender working. I've got my logback config being read and can extend FileAppender w/o issues but when I switch over to RollingFileAppender, I get the following: java.lang.NullPointerException: null at ch.qos.logback.core.rolling.RollingFileAppender.getFile(RollingFileAppender.java:122) ~[org.apache.sling.commons.log:4.0.0] Here is my config: <appender name="CUSTOM" class="com.mypackage.logging.CustomLogAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>log.%d{yyyy-MM-dd}.log</fileNamePattern> </rollingPolicy> <prudent>true</prudent> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> The only method that I override is writeout() as I needed to handle some particular events. Did I missing something obvious in terms of configuration? Any help is appreciated. Thanks! Johny

3 4

Logs lost when rolling
by Germán Ferrari 11 Feb '14

11 Feb '14

Hello. I'm having some strange behaviour with ch.qos.logback.core.rolling.TimeBasedRollingPolicy. I have the same war file deployed in two servers, but in one of them the logs of the day are lost when rolling ... I'm rolling daily at midnight. The modification date of the files in the server with the problem (03:10) coincides with a maintenance job which restarts the webserver. Here is a summary of the files involved: Server where the error occurs: -rw-r--r-- 1 webservd webservd 142 Feb 8 03:10 file.2014-02-07.log -rw-r--r-- 1 webservd webservd 261 Feb 9 03:10 file.2014-02-08.log -rw-r--r-- 1 webservd webservd 2.5K Feb 10 03:10 file.2014-02-09.log -rw-r--r-- 1 webservd webservd 261 Feb 11 03:10 file.2014-02-10.log -rw-r--r-- 1 webservd webservd 1004K Feb 11 12:40 file.log Server where it works ok: -rw-r--r-- 1 webservd webservd 6.7M Feb 7 20:36 file.2014-02-07.log -rw-r--r-- 1 webservd webservd 41K Feb 8 12:10 file.2014-02-08.log -rw-r--r-- 1 webservd webservd 5.8M Feb 10 22:32 file.2014-02-10.log -rw-r--r-- 1 webservd webservd 2.1M Feb 11 12:43 file.log The size of the files should be in the order of the megabytes, but, in the server with the problem, it is in the order of bytes. The contents are just some messages that are written when the application is shutdown, but all the logs of the day are lost ... Any hints of what could be happening? Thank you. Regards, Germán

1 0

browsing dbappender logs
by Chris Cheshire 11 Feb '14

11 Feb '14

I've been using FileAppenders for aeons and want to move my apps (web and headless server apps) to use the DBAppender, but I can't figure out how to view them easily other than hand crafting queries, which is just not sustainable. I looked at the Lilith project and from what I can tell I have to tell my apps to send logs to it, rather than it reading logs already created. Is this correct? I can't add use Lilith to receive logs because I don't want it running all the time just to browse through once a week. What solutions are there for browsing logs stored via a DBAppender? Thanks Chris

1 0

converting from ILoggingEvent to Apache LoggingEvent
by Deepak Singh 11 Feb '14

11 Feb '14

HI All, I have started migrating to logback from log4j.I have encounter issue with a class which is a remote appender(a JMX Mbean). The problem is this class returns the collection of LoggingEvent to remote clients. We are not a position to change the remote clients in near future. Is there any way I can convert ILoggingEvent to LoggingEvent easily. thanks Regards Deepak Singh 1-2 Berner Street London ext : 1907

1 0

ch.qos.logback.classic.sift.GSiftingAppender not found in version 1.1.1
by Rice Yeh 06 Feb '14

06 Feb '14

Hi, just upgrade to version 1.1.1, but an error shows ch.qos.logback.classic.sift.GSiftingAppender not found. I am using groovy to configure logback. In the document, it is mentioned that since 1.0.12, groovy configuration for SiftingAppender is not supported. Then, what is the alternative for newer version?

2 2

Log file is created but it is empty
by Rice Yeh 06 Feb '14

06 Feb '14

I am using logback version 1.0.11 with the following configuration. The log file is created but it is empty. That is, no log messages are put into it? What is wrong with my configuration? appender("close-period", GSiftingAppender) { discriminator(MDCBasedDiscriminator) { key = "period" defaultValue = "unknown" } //timeout = "1 minutes" sift { appender("close-${period}", FileAppender) { file = "${logDir}/close-${period}.log" append = false layout(PatternLayout) { pattern = "%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg%n" } } } } logger("mlm.close_period", INFO, ["close-period"], false) the test code is @Test def testClosePeriod { import org.slf4j.MDC val logger = LoggerFactory.getLogger("mlm.close_period") MDC.put("period", "2014-02") logger.info("testClosePeriod is run") MDC.remove("period") }

1 0

Log file is created successfully but no logging
by bayrak 05 Feb '14

05 Feb '14

With the below configuration settings in my JSF project, I am able to get the logging file but no logging ends at the log file created. See the details: I have the below common configuration for my all JSF project each of which includes its own sl4j and logback libraries. My JSF projects are running on jetty. <configuration scan="true" scanPeriod="30 seconds"> <property name="loggingHome" value="C://server//default//logs" /> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${loggingHome}/${application-name}_log.xml</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${loggingHome}/${application-name}_log.%d{yyyy-MM-dd}.xml%i.gz</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>50MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date %-5level %logger - %msg%n%ex{full}</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="FILE" /> </root> </configuration> I have defined a ServletContextListener and in contextInitialized I have the following piece of code: import javax.servlet.ServletContextEvent; import javax.servlet.ServletContextListener; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.joran.JoranConfigurator; import ch.qos.logback.core.joran.spi.JoranException; import ch.qos.logback.core.util.StatusPrinter; public class LogbackContextInitializer implements ServletContextListener { /* * (non-Javadoc) * * @see javax.servlet.ServletContextListener#contextDestroyed(javax.servlet.ServletContextEvent) */ @Override public void contextDestroyed(ServletContextEvent sce) { } /* * (non-Javadoc) * * @see javax.servlet.ServletContextListener#contextInitialized(javax.servlet.ServletContextEvent) */ @Override public void contextInitialized(ServletContextEvent sce) { LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator jc = new JoranConfigurator(); jc.setContext(context); context.reset(); // override default configuration // inject the name of the current application as "application-name" // property of the LoggerContext context.putProperty("application-name", "myapp"); jc.doConfigure("C://server//default//config//logback.xml"); StatusPrinter.print(context); StatusPrinter.printInCaseOfErrorsOrWarnings(context); Logger log = context.getLogger(LogbackContextInitializer.class); log.error("Hi I am there"); log.debug("Hi I am there"); } catch (JoranException e) { sce.getServletContext().log("Error configuring logback!", e); } } } When application starts, log file is created as I wanted. So, the property application-name is set correctly but no logging is done with Status print or log error. Any idea what I am missing over here. -- View this message in context: http://logback.10977.n7.nabble.com/Log-file-is-created-successfully-but-no-… Sent from the Users mailing list archive at Nabble.com.

1 0

different default log levels for sift logger?
by Norbert Kiesel 01 Feb '14

01 Feb '14

Hi, we are using the sift logger (with MDC) to separate log entries generated by user actions from log entries generated by "background" tasks. That works nicely. However, now we want to have different log levels for these two appenders (e.g. DEBUG for "foreground.log" and WARN for "background.log"). Problem is that there is obviously only one appender. Can that be accomplished within the logback.xml? For reference, here is our current logback.xml <configuration scan="true" scanPeriod="30 seconds"> <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.MDCBasedDiscriminator"> <key>stream</key> <defaultValue>foreground</defaultValue> </discriminator> <sift> <appender name="FILE-${stream}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${destination}/${stream}_current.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${destination}/${stream}_%d{yyyy-MM-dd}.%i.log</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>10MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%date %-5level [%X{token}%thread] %logger{36} [%file:%line] %msg%n</pattern> </encoder> </appender> </sift> </appender> <root level="all"> <appender-ref ref="SIFT" /> </root> </configuration> </nk> --- Norbert Kiesel Systems Architect | Engineering MetricStream 2600 E. Bayshore Road | Palo Alto, CA - 94303 +1-650-620-2954 | nkiesel(a)metricstream.com | www.metricstream.com Confidentiality Notice:This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited

1 0