- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1753) NPE in logback classic module (1.2.11)
by logback developers list 30 Jun '23

30 Jun '23

1 0

[JIRA] Updates for LOGBACK-1753: NPE in logback classic module (1.2.11)
by logback developers list 26 Jun '23

26 Jun '23

logback / LOGBACK-1753 [Open] NPE in logback classic module (1.2.11) ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1753 ============================== Issue created ------------------------------ Charit Saini created this issue on 26/Jun/23 17:26 Summary: NPE in logback classic module (1.2.11) Issue Type: Bug Affects Versions: 1.2.11 Assignee: Logback dev list Components: logback-classic Created: 26/Jun/23 17:26 Environment: OS: CentOS 7 JDK: 11 Spring boot: 2.3.6.RELEASE Spring web/MVC : 5.2.20.RELEASE Tomcat: tomcat-embed-core-9.0.39.jar Priority: Major Reporter: Charit Saini Description: Getting NullPointerException exceptions from Logback classic module. Is it very hard to tell what might be causing it. Also, issues gets after the application restart, and again it starts occurring after an interval. Below are the logs java.lang.NullPointerException: null at ch.qos.logback.classic.Logger.callAppenders(Logger.java:264) 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.info(Logger.java:579) ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1717) Reduce the memory footprint with GraalVM native image
by logback developers list 23 Jun '23

23 Jun '23

1 0

[JIRA] Updates for LOGBACK-1752: SocketReceiver cannot deserialize events in OSGi
by logback developers list 23 Jun '23

23 Jun '23

logback / LOGBACK-1752 [Open] SocketReceiver cannot deserialize events in OSGi ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1752 ============================== Issue created ------------------------------ Joe Shannon created this issue on 23/Jun/23 12:47 Summary: SocketReceiver cannot deserialize events in OSGi Issue Type: Bug Affects Versions: 1.3.8, 1.4.8 Assignee: Logback dev list Components: logback-classic, logback-core Created: 23/Jun/23 12:47 Environment: logback-core and logback-classic in OSGi Priority: Major Reporter: Joe Shannon Description: Using a SocketReceiver in an OSGi environment currently fails when running in OSGi. The event class is ch.qos.logback.classic.spi.LoggingEventVO which is attempted to be deserialized by HardenedObjectInputStream (extends ObjectInputStream). Since HardenedObjectInputStream is in logback-core, the class loader used for deserialization is the bundle loader for ch.qos.logback.core which is unable to load from package ch.qos.logback.classic.spi. A couple of ideas for possible fix: * Add optional Import-Package header for this package * Allow a different class loader to be specified for deserialization ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

regarding LOGBACK-1746
by logback developers list 21 Jun '23

21 Jun '23

Hi all, Has anyone else encountered this issue with the change in when resolution of a JNDI variable occurs? Or is there an alternative configuration that can still achieve what was working in 1.2? Basically I'm using a JNDI variable to define the path to a config file to include: <configuration scan="true"> <insertFromJNDI env-entry-name="java:comp/env/appHome" as="appHome" /> <include file="${appHome}/conf/logback-ssorest.xml"/> </configuration> The logback logs show: 11:12:45,716 |-INFO in ch.qos.logback.classic.LoggerContext[default] - This is logback-classic version 1.4.6 11:12:45,776 |-INFO in ch.qos.logback.core.joran.util.ConfigurationWatchListUtil@354c986c - Adding file:/D:/IDFC/SSORest-3.1-casso/tomcat/bin/appHome_IS_UNDEFINED/conf/logback-ssorest.xml to configuration watch list. 11:12:45,776 |-WARN in ch.qos.logback.core.joran.action.IncludeAction - Failed to open file:/D:/IDFC/SSORest-3.1-casso/tomcat/bin/appHome_IS_UNDEFINED/conf/logback-ssorest.xml 11:12:45,823 |-INFO in ch.qos.logback.core.model.processor.InsertFromJNDIModelHandler - Setting variable [appHome] to [../..] in [LOCAL] scope Any thoughts? BR, Richard [4f117000-5b64-40d3-9b49-7377c6a8c73d]

1 0

[JIRA] Updates for LOGBACK-1750: Compressor.gzCompress() 'done' log msg is wrong - 'ZIP' is logged instead of 'GZ'
by logback developers list 21 Jun '23

21 Jun '23

logback / LOGBACK-1750 [Open] Compressor.gzCompress() 'done' log msg is wrong - 'ZIP' is logged instead of 'GZ' ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1750 ============================== Issue created ------------------------------ Marko Mitrović created this issue on 21/Jun/23 19:21 Summary: Compressor.gzCompress() 'done' log msg is wrong - 'ZIP' is logged instead of 'GZ' Issue Type: Bug Affects Versions: 1.4.8 Assignee: Logback dev list Components: logback-core Created: 21/Jun/23 19:21 Priority: Trivial Reporter: Marko Mitrović Description: Log message in ch.qos.logback.core.rolling.helper.Compressor.gzCompress(String nameOfFile2gz, String nameOfgzedFile) mentions "ZIP" instead of "GZ" ("Done ZIP compressing..."). Start message is ok ("GZ compressing..."). ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1751: StatusPrinter timestamp format should include date
by logback developers list 21 Jun '23

21 Jun '23

logback / LOGBACK-1751 [Open] StatusPrinter timestamp format should include date ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1751 ============================== Issue created ------------------------------ Marko Mitrović created this issue on 21/Jun/23 19:26 Summary: StatusPrinter timestamp format should include date Issue Type: Improvement Affects Versions: 1.4.8 Assignee: Logback dev list Components: logback-core Created: 21/Jun/23 19:26 Priority: Minor Reporter: Marko Mitrović Description: Logback's own status log messages show timestamp as time only ('HH:mm:ss,SSS'). Showing the date part would be very helpful when browsing multi-day status log files (format suggestion: 'yyyy-MM-dd HH:mm:ss,SSS'). ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1749: In the new JsonEncoder, the throwable's cause(s) are not included.
by logback developers list 21 Jun '23

21 Jun '23

logback / LOGBACK-1749 [Open] In the new JsonEncoder, the throwable's cause(s) are not included. ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1749 ============================== Issue created ------------------------------ Christopher Holt created this issue on 21/Jun/23 17:55 Summary: In the new JsonEncoder, the throwable's cause(s) are not included. Issue Type: Bug Affects Versions: 1.3.8 Assignee: Logback dev list Components: logback-classic Created: 21/Jun/23 17:55 Environment: logback 1.3.8, running in tomcat. Labels: logging Priority: Major Reporter: Christopher Holt Description: With this appender: <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="ch.qos.logback.classic.encoder.JsonEncoder"/> </appender> The throwable that get get encoded only has it's immediate stack trace. It needs to include the throwable's cause (recursively, maybe up to some sanity limit?) ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] Updates for LOGBACK-1748: JsonEncoder: allow configuring to get formatted message in the json payload
by logback developers list 21 Jun '23

21 Jun '23

logback / LOGBACK-1748 [Open] JsonEncoder: allow configuring to get formatted message in the json payload ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1748 ============================== Issue created ------------------------------ Bruno Ballekens created this issue on 21/Jun/23 17:08 Summary: JsonEncoder: allow configuring to get formatted message in the json payload Issue Type: Improvement Affects Versions: 1.4.8 Assignee: Logback dev list Components: logback-classic Created: 21/Jun/23 17:08 Priority: Major Reporter: Bruno Ballekens Description: JsonEncoder currently does not put the formatted message in the json payload. It puts the message and the argument array. Some of the libs we use, do log using the message format based methods, which now look strange in our log aggregation system (sometimes we even see {} as the message with then the actual message as the single member of the argument array). Would it be possible to make JsonEncoder configurable to put the formatted message in the json payload with `message` key ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1711) Deadlock when using Virtual Threads
by logback developers list 21 Jun '23

21 Jun '23

1 0