September 2018 - logback-dev

[JIRA] (LOGBACK-1426) JMS Queue Appender
by QOS.CH (JIRA) 25 Sep '18

25 Sep '18

Sudhik created LOGBACK-1426: ------------------------------- Summary: JMS Queue Appender Key: LOGBACK-1426 URL: https://jira.qos.ch/browse/LOGBACK-1426 Project: logback Issue Type: Bug Components: logback-access Affects Versions: 1.2.1 Environment: Container: Liberty Profile <feature>wasJmsClient-2.0</feature> <resourceAdapter id="mqJms" location="$\{server.config.dir}/jars/wmq/wmq.jmsra-9.0.4.0.rar"> <classloader apiTypeVisibility="spec, ibm-api, api, third-party"/> </resourceAdapter> <jmsQueueConnectionFactory id="jndi/MDBQ" jndiName="jndi/MDBQ"> <properties.mqJms channel="APPL_CONN_CHL" hostName="QMAPPPRD.azlifem.azl.pvt" port="1414" queueManager="QM.APP.PRD" transportType="CLIENT" /> </jmsQueueConnectionFactory> <jmsQueue id="jndi/queue" jndiName="jndi/queue"> <properties.mqJms baseQueueName="ELFSERVICE.APP" baseQueueManagerName="QM.APP.PRD" /> </jmsQueue> logback.xml <appender name="queue" class="ch.qos.logback.classic.net.JMSQueueAppender"> <QueueConnectionFactoryBindingName>jndi/MDBQ</QueueConnectionFactoryBindingName> <QueueBindingName>jndi/queue</QueueBindingName> </appender> Logs: 15:06:04,590 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.net.JMSQueueAppender] 15:06:04,591 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [queue] [9/25/18 15:06:05:026 CDT] 00000018 SystemOut O 2018-09-25 15:06:05,025 [Default Executor-thread-1] INFO JMS_LOGGER - Message sent to the configured appender. Reporter: Sudhik Assignee: Logback dev list I need to user JMS Queue Appender and implemented it using 1.2.1 version of logback-access. Logs say appender is added and messages are being sent to queue successfully but I don't actually see the messages in queue. When I write a small program to write the messages to queue using the code of logback-access, it successfully writes. So, no idea on where logback is failing. Do you plan to release any new version of Logback with JMS appender or can you look at why my code is not working ? -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1425) logback implementation leaves .tmp file while rolling
by QOS.CH (JIRA) 24 Sep '18

24 Sep '18

Mukesh created LOGBACK-1425: ------------------------------- Summary: logback implementation leaves .tmp file while rolling Key: LOGBACK-1425 URL: https://jira.qos.ch/browse/LOGBACK-1425 Project: logback Issue Type: Bug Environment: Production Reporter: Mukesh Assignee: Logback dev list While rolling the file name we are getting .tmp files along with the zipped files. My implementation of logback is as below <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="30 seconds" debug="true">  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d\{HH:mm:ss.SSS} [%thread] %-5level %logger\{5} - %msg%n </pattern> </encoder> </appender> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/usr/local/apache-tomcat-7.0.55/logs/mylog.log </file>  <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/usr/local/apache-tomcat-7.0.55/logs/mylog_%d\{yyyyMMddHHmmss}.%i.log.gz </fileNamePattern>  <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>20MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>2</maxHistory> </rollingPolicy> <encoder> <charset>UTF-8</charset> <pattern>%d %-4relative [%thread] %-5level %logger\{35} - %msg%n </pattern> </encoder> </appender> <appender name="GANASEVAFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/usr/local/apache-tomcat-7.0.55/logs/AbcComm/abcComm.log </file>  <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/usr/local/apache-tomcat-7.0.55/logs/AbcComm/abcComm_%d\{yyyy-MM-dd}.%i.log.gz </fileNamePattern>  <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>20MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>2</maxHistory> </rollingPolicy> <encoder> <charset>UTF-8</charset> <pattern>%d %-4relative [%thread] %-5level %logger\{35} - %msg%n </pattern> </encoder> </appender> <logger name="org.hibernate.type" level="ERROR" /> <logger name="org.hibernate.SQL" level="ERROR" /> <logger name="org.hibernate" level="ERROR" /> <logger name="org.springframework.transaction" level="ERROR" /> <logger name="org.springframework.orm" level="ERROR" /> <logger name="org.springframework" level="ERROR" /> <logger name="com.scl.ganaseva.db.communicator" level="DEBUG"> <appender-ref ref="GANASEVAFILE" /> </logger> <logger name="com.rbl.framework.sms" level="DEBUG"> <appender-ref ref="FILE" /> </logger>  <root level="DEBUG"> <appender-ref ref="FILE" /> </root> </configuration> -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1201) totalSizeCap not delete the oldest 1 day in maxHistory
by QOS.CH (JIRA) 24 Sep '18

24 Sep '18

1 0

[JIRA] (LOGBACK-1424) high contention at ch.qos.logback.core.AsyncAppenderBase.putUninterruptibly
by QOS.CH (JIRA) 17 Sep '18

17 Sep '18

Jamie created LOGBACK-1424: ------------------------------ Summary: high contention at ch.qos.logback.core.AsyncAppenderBase.putUninterruptibly Key: LOGBACK-1424 URL: https://jira.qos.ch/browse/LOGBACK-1424 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: Linux server.com 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Reporter: Jamie Assignee: Logback dev list Attachments: cat.zip Disclaimer: I am not sure this is a bug (please excuse if not the case and it is fault in our code somewhere). However, our server stopped processing data yesterday. All threads were found waiting on AsyncAppenderBase.putUninterruptibly. Stack trace outputted below. To see a comprehensive snapshot of all threads, please visit [http://fastthread.io/] and upload the attached cat.zip file. Click on the filequeue-worker link in the Thread Group section to see the problem. {code:java} worker-374 - priority:5 - threadId:0x00007fe456176000 - nativeId:0x313 - state:WAITING stackTrace: java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x0000000646f11d48> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) at java.util.concurrent.ArrayBlockingQueue.put(ArrayBlockingQueue.java:353) at ch.qos.logback.core.AsyncAppenderBase.putUninterruptibly(AsyncAppenderBase.java:181) at ch.qos.logback.core.AsyncAppenderBase.put(AsyncAppenderBase.java:172) at ch.qos.logback.core.AsyncAppenderBase.append(AsyncAppenderBase.java:161) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:84) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:270) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:257) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:421) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383) at ch.qos.logback.classic.Logger.error(Logger.java:522) {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1423) Executing jdeps on logback-classic-1.3.0-alpha fails
by QOS.CH (JIRA) 16 Sep '18

16 Sep '18

Janek created LOGBACK-1423: ------------------------------ Summary: Executing jdeps on logback-classic-1.3.0-alpha fails Key: LOGBACK-1423 URL: https://jira.qos.ch/browse/LOGBACK-1423 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha4, 1.3.0-alpha3, 1.3.0-alpha1, 1.3.0-alpha0 Environment: Kubuntu 18.04 Reporter: Janek Assignee: Logback dev list Executing jdeps from JDK 10 on any of the alpha versions of logback leads to this error, which currently hinders me from creating a self-contained application with the newer version: \{code:java} $ jdeps logback-classic-1.3.0-alpha4.jar Exception in thread "main" java.lang.module.FindException: Module ch.qos.logback.core not found, required by ch.qos.logback.classic at java.base/java.lang.module.Resolver.findFail(Resolver.java:877) at java.base/java.lang.module.Resolver.resolve(Resolver.java:191) at java.base/java.lang.module.Resolver.resolve(Resolver.java:140) at java.base/java.lang.module.Configuration.resolve(Configuration.java:411) at java.base/java.lang.module.Configuration.resolve(Configuration.java:245) at jdk.jdeps/com.sun.tools.jdeps.JdepsConfiguration.<init>(JdepsConfiguration.java:116) at jdk.jdeps/com.sun.tools.jdeps.JdepsConfiguration.<init>(JdepsConfiguration.java:67) at jdk.jdeps/com.sun.tools.jdeps.JdepsConfiguration$Builder.build(JdepsConfiguration.java:577) at jdk.jdeps/com.sun.tools.jdeps.JdepsTask.buildConfig(JdepsTask.java:589) at jdk.jdeps/com.sun.tools.jdeps.JdepsTask.run(JdepsTask.java:543) at jdk.jdeps/com.sun.tools.jdeps.JdepsTask.run(JdepsTask.java:519) at jdk.jdeps/com.sun.tools.jdeps.Main.main(Main.java:49) \{code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1422) Deadlock with logging
by QOS.CH (JIRA) 15 Sep '18

15 Sep '18

1 0

[JIRA] (LOGBACK-1422) Deadlock with logging
by QOS.CH (JIRA) 14 Sep '18

14 Sep '18

1 0

[JIRA] (LOGBACK-1422) Deadlock with logging
by QOS.CH (JIRA) 14 Sep '18

14 Sep '18

1 0

[JIRA] (LOGBACK-1422) Deadlock with logging
by QOS.CH (JIRA) 14 Sep '18

14 Sep '18

1 0

[JIRA] (LOGBACK-1422) Deadlock with logging
by QOS.CH (JIRA) 14 Sep '18

14 Sep '18

1 0