June 2017 - logback-dev - mailman3.qos.ch

Missing maven artifacts for logback-core 1.2.3
by Matthew.Webber＠Diamond.ac.uk 15 Jun '17

15 Jun '17

On Maven Central, artifacts are available: For logback-classic 1.2.3 http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22ch.qos.logback%22%20AND%2… But for logback-core, only 1.2.2 is available: http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22ch.qos.logback%22%20AND%2… Was something missed in the release process? Thanks Matthew -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

1 0

[JIRA] (LOGBACK-1315) MAX_POOL_SIZE for ScheduledThreadPoolExecutor is not configurable
by QOS.CH (JIRA) 14 Jun '17

14 Jun '17

Michael Price created LOGBACK-1315: -------------------------------------- Summary: MAX_POOL_SIZE for ScheduledThreadPoolExecutor is not configurable Key: LOGBACK-1315 URL: https://jira.qos.ch/browse/LOGBACK-1315 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Michael Price Assignee: Logback dev list Priority: Minor We're utilizing Logback in an Java application that is fairly memory constrained. It is important for us to be able to configure/constrain the number of threads that Logback can utilize. Specifically, we would like to be able to tune the value of CoreConstants.MAX_POOL_SIZE. Relevant changes are in https://jira.qos.ch/browse/LOGBACK-1238. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1314) NumberFormatException: For input string: "-"
by QOS.CH (JIRA) 14 Jun '17

14 Jun '17

Sankha Subhra Ghosh created LOGBACK-1314: -------------------------------------------- Summary: NumberFormatException: For input string: "-" Key: LOGBACK-1314 URL: https://jira.qos.ch/browse/LOGBACK-1314 Project: logback Issue Type: Bug Components: Joran, logback-classic Affects Versions: 1.2.3 Environment: Development Reporter: Sankha Subhra Ghosh Assignee: Logback dev list I need to print the class, method and line number in the logger. FOr that I am using the following entry: {code:java} <appender name="ErrorFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${stb.log.dir}eFaktura.error.detaljert.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${stb.log.dir}eFaktura.error.detaljert.%d{yyyy-MM-dd}.%i.log</fileNamePattern> <maxHistory>3</maxHistory>  <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <MaxFileSize>10MB</MaxFileSize> </TimeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern> %d %-5p [%X{sessionId}] [%X{userId}] %C{1}.%-M:%L] %m%n </Pattern> </encoder>  </appender> <root level="ERROR"> <appender-ref ref="ErrorFileAppender" /> </root> {code} As you can see, my pattern is {code:java} %d %-5p [%X{sessionId}] [%X{userId}] %C{1}.%-M:%L] %m%n{code} Then I am getting the following error: {code:java} 09:31:44,119 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@29:19 - RuntimeException in Action for tag [encoder] java.lang.NumberFormatException: For input string: "-" at java.lang.NumberFormatException: For input string: "-" at at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at at java.lang.Integer.parseInt(Integer.java:572) at at java.lang.Integer.parseInt(Integer.java:615) at at ch.qos.logback.core.pattern.FormatInfo.valueOf(FormatInfo.java:73) at at ch.qos.logback.core.pattern.parser.Parser.T(Parser.java:136) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:96) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:115) at at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:100) at at ch.qos.logback.core.pattern.parser.Parser.parse(Parser.java:91) at at ch.qos.logback.core.pattern.PatternLayoutBase.start(PatternLayoutBase.java:83) at at ch.qos.logback.classic.encoder.PatternLayoutEncoder.start(PatternLayoutEncoder.java:28) at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:161) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:309) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:193) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:179) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:165) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:152) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357) at at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155) at at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132) at at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:273) at at org.springframework.context.support.AbstractApplicationContext.<init>(AbstractApplicationContext.java:164) at at org.springframework.context.support.AbstractApplicationContext.<init>(AbstractApplicationContext.java:228) at at org.springframework.context.support.AbstractRefreshableApplicationContext.<init>(AbstractRefreshableApplicationContext.java:89) at at org.springframework.context.support.AbstractRefreshableConfigApplicationContext.<init>(AbstractRefreshableConfigApplicationContext.java:58) at at org.springframework.context.support.AbstractXmlApplicationContext.<init>(AbstractXmlApplicationContext.java:61) at at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:136) at at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83) {code} But if I use {code:java} %d %-5p [%X{sessionId}] [%X{userId}] %m%n{code} Then there is no error. Can someone please take a look. Here is my pom entry: {code:java} <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.7.25</version> </dependency> <dependency> <groupId>org.logback-extensions</groupId> <artifactId>logback-ext-spring</artifactId> <version>0.1.4</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.2.3</version> <scope>test</scope> </dependency> {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1313) RollingFileAppender / SizeBasedTriggeringPolicy : filename with character "-' is not rolled over
by QOS.CH (JIRA) 12 Jun '17

12 Jun '17

1 0

[JIRA] (LOGBACK-1313) RollingFileAppender / SizeBasedTriggeringPolicy : filename with character "-' is not rolled over
by QOS.CH (JIRA) 12 Jun '17

12 Jun '17

Abdelhafid Allou created LOGBACK-1313: ----------------------------------------- Summary: RollingFileAppender / SizeBasedTriggeringPolicy : filename with character "-' is not rolled over Key: LOGBACK-1313 URL: https://jira.qos.ch/browse/LOGBACK-1313 Project: logback Issue Type: Bug Environment: Reporter: Abdelhafid Allou Assignee: Logback dev list I have a problem with rolling over files when i use RollingFileAppender, when my filename contains the "-" chacarter. Example : {code:java} <appender name="LOG-FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${LOG_ROOT_PATH}/my-file.log</file> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>%d{yyyyMMddHHmmss}|%msg%n</Pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>${LOG_ROOT_PATH}/my-file.%i.log</fileNamePattern> <maxHistory>10</maxHistory> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1MB</maxFileSize> </triggeringPolicy> </appender>{code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 12 Jun '17

12 Jun '17

1 0

[JIRA] (LOGBACK-1312) Tomcat 8.5.14 reports stale thread created by Logback
by QOS.CH (JIRA) 08 Jun '17

08 Jun '17

Michael Osipov created LOGBACK-1312: --------------------------------------- Summary: Tomcat 8.5.14 reports stale thread created by Logback Key: LOGBACK-1312 URL: https://jira.qos.ch/browse/LOGBACK-1312 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.2 Environment: Apache Tomcat/8.5.14, Java 8 Reporter: Michael Osipov Assignee: Logback dev list Tomcat tells me: {noformat} 2017-06-04T01:00:09.200 WARNUNG [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [tedab-services] appears to have started a thread named [logback-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:458) java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362) java.util.concurrent.SynchronousQueue.take(SynchronousQueue.java:924) java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745) {noformat} My {{logack.xml}} is: {code:xml} <configuration> <insertFromJNDI env-entry-name="java:comp/env/context/baseName" as="contextName" /> <contextName>${contextName}</contextName> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${catalina.base}/logs/${CONTEXT_NAME}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${catalina.base}/logs/${CONTEXT_NAME}.log.%d.gz</fileNamePattern> <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="FILE" /> </root> <logger name="com.company" level="INFO" /> <logger name="org.springframework" level="WARN" /> </configuration> {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1293) Error with simultaneous %d and %i in RollingFileAppender and FixedWindowRollingPolicy
by QOS.CH (JIRA) 08 Jun '17

08 Jun '17

1 0

[JIRA] (LOGBACK-1306) Detect logback.ContextSelector in System environment
by QOS.CH (JIRA) 07 Jun '17

07 Jun '17

1 0

[JIRA] (LOGBACK-1311) SizeAndTimeBasedRollingPolicy can config minIndex and maxIndex
by QOS.CH (JIRA) 07 Jun '17

07 Jun '17

finalmachine created LOGBACK-1311: ------------------------------------- Summary: SizeAndTimeBasedRollingPolicy can config minIndex and maxIndex Key: LOGBACK-1311 URL: https://jira.qos.ch/browse/LOGBACK-1311 Project: logback Issue Type: New Feature Components: logback-core Affects Versions: 1.2.3 Reporter: finalmachine Assignee: Logback dev list {color:#333333}SizeAndTimeBasedRollingPolicy need fileNamePattern has {color}{color:#0080c0}{color:#333333}integer token %i, but if I want to conf %i as FixedWindowRollingPolicy,there is no way,so could logback provide minIndex and maxIndex in config file{color} {color} {color:#000080} {color} {color:#008000} {color} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0