From logback-dev at qos.ch  Fri Jun  9 19:01:07 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 09 Jun 2023 13:01:07 -0400
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
Message-ID: <mailman.2142.1686330074.23762.logback-dev@qos.ch>

Before 1.3, the class StaticLoggerBinder had an init method that would in turn call the init method on the singleton ContextSelectorBinder:

contextSelectorBinder.init(defaultLoggerContext, KEY);


-Richard
[48c29399-04ec-4cd1-8794-c7507a7d5ded]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230609/e956c1c8/attachment.htm>

From logback-dev at qos.ch  Fri Jun  9 19:07:23 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 9 Jun 2023 19:07:23 +0200
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
In-Reply-To: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
References: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
Message-ID: <mailman.2143.1686330445.23762.logback-dev@qos.ch>


Hello Richard,

StaticLoggerBinder has been replaced by
org.slf4j.spi.SLF4JServiceProvider of which LogbackServiceProvider is an
implementation.

SLF4JServiceProvider interface has a method called initialize().

Is this what you were asking?

-- 
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

On 6/9/2023 7:01 PM, logback developers list via logback-dev wrote:
> Before 1.3, the class StaticLoggerBinder had an init method that would
> in turn call the init method on the singleton ContextSelectorBinder:
> 
> contextSelectorBinder.init(defaultLoggerContext, KEY);
> 
> -Richard
> 48c29399-04ec-4cd1-8794-c7507a7d5ded

From logback-dev at qos.ch  Fri Jun  9 19:27:37 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 09 Jun 2023 13:27:37 -0400
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
In-Reply-To: <mailman.2143.1686330445.23762.logback-dev@qos.ch>
References: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
 <mailman.2143.1686330445.23762.logback-dev@qos.ch>
Message-ID: <mailman.2149.1686331665.23762.logback-dev@qos.ch>

Yeah my issue is that I have a unit test that checks if ContextSelectorStaticBinder is properly configured to return our custom ContextSelector and I'm not sure what to replace that with.

        ContextSelector selector = ContextSelectorStaticBinder.getSingleton().getContextSelector();
        assertTrue(selector instanceof FrameworkLoggerContextSelector);

getContextSelector() now returns null in my unit test.

BR,

Richard
On 6/9/2023 1:07:26 PM, logback developers list via logback-dev <logback-dev at qos.ch> wrote:

Hello Richard,

StaticLoggerBinder has been replaced by
org.slf4j.spi.SLF4JServiceProvider of which LogbackServiceProvider is an
implementation.

SLF4JServiceProvider interface has a method called initialize().

Is this what you were asking?

--
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

On 6/9/2023 7:01 PM, logback developers list via logback-dev wrote:
> Before 1.3, the class StaticLoggerBinder had an init method that would
> in turn call the init method on the singleton ContextSelectorBinder:
>
> contextSelectorBinder.init(defaultLoggerContext, KEY);
>
> -Richard
> 48c29399-04ec-4cd1-8794-c7507a7d5ded
_______________________________________________
logback-dev mailing list
logback-dev at qos.ch
https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
[17fa5a94-06c8-464e-bde9-1843e17d88e4]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230609/f2f82ec7/attachment-0001.htm>

From logback-dev at qos.ch  Fri Jun  9 19:51:20 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 9 Jun 2023 19:51:20 +0200
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
In-Reply-To: <mailman.2149.1686331665.23762.logback-dev@qos.ch>
References: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
 <mailman.2143.1686330445.23762.logback-dev@qos.ch>
 <mailman.2149.1686331665.23762.logback-dev@qos.ch>
Message-ID: <mailman.2158.1686333081.23762.logback-dev@qos.ch>


During 1.3 development, there was a simplification effort and support
for context selectors was dropped due to lack of interest.

Having said this, you can create your own implementation of
SLF4JServiceProvider overriding LogbackServiceProvider.


On 6/9/2023 7:27 PM, logback developers list via logback-dev wrote:
> Yeah my issue is that I have a unit test that checks if
> ContextSelectorStaticBinder is properly configured to return our custom
> ContextSelector and I'm not sure what to replace that with.
> 
>         ContextSelector selector =
> ContextSelectorStaticBinder.getSingleton().getContextSelector();
>         assertTrue(selector instanceof FrameworkLoggerContextSelector);
> 
> getContextSelector() now returns null in my unit test.
> 
> BR,
> 
> Richard
>>
>> On 6/9/2023 1:07:26 PM, logback developers list via logback-dev
>> <logback-dev at qos.ch> wrote:
>>
>>
>> Hello Richard,
>>
>> StaticLoggerBinder has been replaced by
>> org.slf4j.spi.SLF4JServiceProvider of which LogbackServiceProvider is an
>> implementation.
>>
>> SLF4JServiceProvider interface has a method called initialize().
>>
>> Is this what you were asking?
>>
>> -- 
>> Ceki Gülcü
>>
>> Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
>>
>> On 6/9/2023 7:01 PM, logback developers list via logback-dev wrote:
>> > Before 1.3, the class StaticLoggerBinder had an init method that would
>> > in turn call the init method on the singleton ContextSelectorBinder:
>> >
>> > contextSelectorBinder.init(defaultLoggerContext, KEY);
>> >
>> > -Richard
>> > 48c29399-04ec-4cd1-8794-c7507a7d5ded
>> _______________________________________________
>> logback-dev mailing list
>> logback-dev at qos.ch
>> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
> 17fa5a94-06c8-464e-bde9-1843e17d88e4
> 
> _______________________________________________
> logback-dev mailing list
> logback-dev at qos.ch
> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev

-- 
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

From logback-dev at qos.ch  Fri Jun  9 19:59:54 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 09 Jun 2023 13:59:54 -0400
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
In-Reply-To: <mailman.2158.1686333081.23762.logback-dev@qos.ch>
References: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
 <mailman.2143.1686330445.23762.logback-dev@qos.ch>
 <mailman.2149.1686331665.23762.logback-dev@qos.ch>
 <mailman.2158.1686333081.23762.logback-dev@qos.ch>
Message-ID: <mailman.2159.1686333602.23762.logback-dev@qos.ch>

Does that mean that ContextSelector will be removed entirely at some point?
On 6/9/2023 1:51:45 PM, logback developers list via logback-dev <logback-dev at qos.ch> wrote:

During 1.3 development, there was a simplification effort and support
for context selectors was dropped due to lack of interest.

Having said this, you can create your own implementation of
SLF4JServiceProvider overriding LogbackServiceProvider.


On 6/9/2023 7:27 PM, logback developers list via logback-dev wrote:
> Yeah my issue is that I have a unit test that checks if
> ContextSelectorStaticBinder is properly configured to return our custom
> ContextSelector and I'm not sure what to replace that with.
>
>         ContextSelector selector =
> ContextSelectorStaticBinder.getSingleton().getContextSelector();
>         assertTrue(selector instanceof FrameworkLoggerContextSelector);
>
> getContextSelector() now returns null in my unit test.
>
> BR,
>
> Richard
>>
>> On 6/9/2023 1:07:26 PM, logback developers list via logback-dev
>> wrote:
>>
>>
>> Hello Richard,
>>
>> StaticLoggerBinder has been replaced by
>> org.slf4j.spi.SLF4JServiceProvider of which LogbackServiceProvider is an
>> implementation.
>>
>> SLF4JServiceProvider interface has a method called initialize().
>>
>> Is this what you were asking?
>>
>> --
>> Ceki Gülcü
>>
>> Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
>>
>> On 6/9/2023 7:01 PM, logback developers list via logback-dev wrote:
>> > Before 1.3, the class StaticLoggerBinder had an init method that would
>> > in turn call the init method on the singleton ContextSelectorBinder:
>> >
>> > contextSelectorBinder.init(defaultLoggerContext, KEY);
>> >
>> > -Richard
>> > 48c29399-04ec-4cd1-8794-c7507a7d5ded
>> _______________________________________________
>> logback-dev mailing list
>> logback-dev at qos.ch
>> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
> 17fa5a94-06c8-464e-bde9-1843e17d88e4
>
> _______________________________________________
> logback-dev mailing list
> logback-dev at qos.ch
> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev

--
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
_______________________________________________
logback-dev mailing list
logback-dev at qos.ch
https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
[653eb924-9acd-40d5-8a50-ec40d5128862]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230609/4ac0322a/attachment.htm>

From logback-dev at qos.ch  Fri Jun  9 20:03:51 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 9 Jun 2023 20:03:51 +0200
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
In-Reply-To: <mailman.2159.1686333602.23762.logback-dev@qos.ch>
References: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
 <mailman.2143.1686330445.23762.logback-dev@qos.ch>
 <mailman.2149.1686331665.23762.logback-dev@qos.ch>
 <mailman.2158.1686333081.23762.logback-dev@qos.ch>
 <mailman.2159.1686333602.23762.logback-dev@qos.ch>
Message-ID: <mailman.2161.1686333843.23762.logback-dev@qos.ch>

Currently, ContextSelector is not used and is considered vestigial. It
can be reintroduced depending on user interest.

On 6/9/2023 7:59 PM, logback developers list via logback-dev wrote:
> Does that mean that ContextSelector will be removed entirely at some point?
>>
>> On 6/9/2023 1:51:45 PM, logback developers list via logback-dev
>> <logback-dev at qos.ch> wrote:
>>
>>
>> During 1.3 development, there was a simplification effort and support
>> for context selectors was dropped due to lack of interest.
>>
>> Having said this, you can create your own implementation of
>> SLF4JServiceProvider overriding LogbackServiceProvider.
>>
>>
>> On 6/9/2023 7:27 PM, logback developers list via logback-dev wrote:
>> > Yeah my issue is that I have a unit test that checks if
>> > ContextSelectorStaticBinder is properly configured to return our custom
>> > ContextSelector and I'm not sure what to replace that with.
>> >
>> >         ContextSelector selector =
>> > ContextSelectorStaticBinder.getSingleton().getContextSelector();
>> >         assertTrue(selector instanceof FrameworkLoggerContextSelector);
>> >
>> > getContextSelector() now returns null in my unit test.
>> >
>> > BR,
>> >
>> > Richard
>> >>
>> >> On 6/9/2023 1:07:26 PM, logback developers list via logback-dev
>> >> wrote:
>> >>
>> >>
>> >> Hello Richard,
>> >>
>> >> StaticLoggerBinder has been replaced by
>> >> org.slf4j.spi.SLF4JServiceProvider of which LogbackServiceProvider
>> is an
>> >> implementation.
>> >>
>> >> SLF4JServiceProvider interface has a method called initialize().
>> >>
>> >> Is this what you were asking?
>> >>
>> >> --
>> >> Ceki Gülcü
>> >>
>> >> Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
>> >>
>> >> On 6/9/2023 7:01 PM, logback developers list via logback-dev wrote:
>> >> > Before 1.3, the class StaticLoggerBinder had an init method that
>> would
>> >> > in turn call the init method on the singleton ContextSelectorBinder:
>> >> >
>> >> > contextSelectorBinder.init(defaultLoggerContext, KEY);
>> >> >
>> >> > -Richard
>> >> > 48c29399-04ec-4cd1-8794-c7507a7d5ded
>> >> _______________________________________________
>> >> logback-dev mailing list
>> >> logback-dev at qos.ch
>> >> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
>> > 17fa5a94-06c8-464e-bde9-1843e17d88e4
>> >
>> > _______________________________________________
>> > logback-dev mailing list
>> > logback-dev at qos.ch
>> > https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
>>
>> -- 
>> Ceki Gülcü
>>
>> Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
>> _______________________________________________
>> logback-dev mailing list
>> logback-dev at qos.ch
>> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
> 653eb924-9acd-40d5-8a50-ec40d5128862
> 
> _______________________________________________
> logback-dev mailing list
> logback-dev at qos.ch
> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev

-- 
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

From logback-dev at qos.ch  Fri Jun  9 21:44:19 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 09 Jun 2023 15:44:19 -0400
Subject: [logback-dev] what replaced StaticLoggerBinder to invoke
 ContextSelectorStaticBinder.init()?
In-Reply-To: <mailman.2161.1686333843.23762.logback-dev@qos.ch>
References: <mailman.2142.1686330074.23762.logback-dev@qos.ch>
 <mailman.2143.1686330445.23762.logback-dev@qos.ch>
 <mailman.2149.1686331665.23762.logback-dev@qos.ch>
 <mailman.2158.1686333081.23762.logback-dev@qos.ch>
 <mailman.2159.1686333602.23762.logback-dev@qos.ch>
 <mailman.2161.1686333843.23762.logback-dev@qos.ch>
Message-ID: <mailman.2164.1686339866.23762.logback-dev@qos.ch>

We certainly have relied on it up until now, but it looks like we can put the logic from our custom ContextSelector into an SLF4JServiceProvider.

Thanks for your help!

BR,

Richard
On 6/9/2023 2:04:04 PM, logback developers list via logback-dev <logback-dev at qos.ch> wrote:
Currently, ContextSelector is not used and is considered vestigial. It
can be reintroduced depending on user interest.

On 6/9/2023 7:59 PM, logback developers list via logback-dev wrote:
> Does that mean that ContextSelector will be removed entirely at some point?
>>
>> On 6/9/2023 1:51:45 PM, logback developers list via logback-dev
>> wrote:
>>
>>
>> During 1.3 development, there was a simplification effort and support
>> for context selectors was dropped due to lack of interest.
>>
>> Having said this, you can create your own implementation of
>> SLF4JServiceProvider overriding LogbackServiceProvider.
>>
>>
>> On 6/9/2023 7:27 PM, logback developers list via logback-dev wrote:
>> > Yeah my issue is that I have a unit test that checks if
>> > ContextSelectorStaticBinder is properly configured to return our custom
>> > ContextSelector and I'm not sure what to replace that with.
>> >
>> >         ContextSelector selector =
>> > ContextSelectorStaticBinder.getSingleton().getContextSelector();
>> >         assertTrue(selector instanceof FrameworkLoggerContextSelector);
>> >
>> > getContextSelector() now returns null in my unit test.
>> >
>> > BR,
>> >
>> > Richard
>> >>
>> >> On 6/9/2023 1:07:26 PM, logback developers list via logback-dev
>> >> wrote:
>> >>
>> >>
>> >> Hello Richard,
>> >>
>> >> StaticLoggerBinder has been replaced by
>> >> org.slf4j.spi.SLF4JServiceProvider of which LogbackServiceProvider
>> is an
>> >> implementation.
>> >>
>> >> SLF4JServiceProvider interface has a method called initialize().
>> >>
>> >> Is this what you were asking?
>> >>
>> >> --
>> >> Ceki Gülcü
>> >>
>> >> Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
>> >>
>> >> On 6/9/2023 7:01 PM, logback developers list via logback-dev wrote:
>> >> > Before 1.3, the class StaticLoggerBinder had an init method that
>> would
>> >> > in turn call the init method on the singleton ContextSelectorBinder:
>> >> >
>> >> > contextSelectorBinder.init(defaultLoggerContext, KEY);
>> >> >
>> >> > -Richard
>> >> > 48c29399-04ec-4cd1-8794-c7507a7d5ded
>> >> _______________________________________________
>> >> logback-dev mailing list
>> >> logback-dev at qos.ch
>> >> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
>> > 17fa5a94-06c8-464e-bde9-1843e17d88e4
>> >
>> > _______________________________________________
>> > logback-dev mailing list
>> > logback-dev at qos.ch
>> > https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
>>
>> --
>> Ceki Gülcü
>>
>> Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
>> _______________________________________________
>> logback-dev mailing list
>> logback-dev at qos.ch
>> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
> 653eb924-9acd-40d5-8a50-ec40d5128862
>
> _______________________________________________
> logback-dev mailing list
> logback-dev at qos.ch
> https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev

--
Ceki Gülcü

Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
_______________________________________________
logback-dev mailing list
logback-dev at qos.ch
https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
[a636fbe9-aed4-45b7-b697-376e6da57e3b]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230609/a3dc5f3b/attachment-0001.htm>

From logback-dev at qos.ch  Sun Jun 11 06:28:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Sun, 11 Jun 2023 06:28:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1744: Reload logback.xml
 on changes to any specified properties files
In-Reply-To: <JIRA.17124.1686457044000@Atlassian.JIRA>
References: <JIRA.17124.1686457044000@Atlassian.JIRA>
 <JIRA.17124.1686457044638@yvo>
Message-ID: <mailman.2184.1686457681.23762.logback-dev@qos.ch>

logback / LOGBACK-1744 [Open]
Reload logback.xml on changes to any specified properties files

==============================

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-1744

==============================
 Issue created
------------------------------

David M. Karr created this issue on 11/Jun/23 6:17

Summary:              Reload logback.xml on changes to any specified properties files
Issue Type:           New Feature
Assignee:             Logback dev list
Components:           logback-core
Created:              11/Jun/23 6:17
Priority:             Minor
Reporter:             David M. Karr
Description:
  We deploy many similar services using logback to k8s clusters. The logback.xml in each service specifies one or more properties files with a "property" element and "file" attribute.  our logback.xml files specify "scan=true" and "scanPeriod=5 seconds". Our logback.xml files also "include" a "base" logback.xml that defines structures used by every service.
  
  When we dynamically modify, or just touch, either the logback.xml or the "base" logback.xml, it reloads the logback.xml and integrates any dynamic changes.
  
  However, if we instead just modify the properties file, nothing happens.  It doesn't reload the logback.xml and process the new properties file content. After we modify the properties file, if we then modify the logback.xml, then it reloads everything, including the new properties file content.
  
  I asked about this situation in the logback-user list, and Ceki pretty quickly indicated that this observation is correct, but it wasn't done intentionally, it is simply an omission.  He said I should file a ticket to request this, so that's what I'm doing.
  
  Logback should watch for changes to specified properties files the same way it looks for changes to the logback.xml and any other included xml files.


==============================
 This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)


From logback-dev at qos.ch  Tue Jun 13 13:23:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Tue, 13 Jun 2023 13:23:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1734) Add support for NDJSON /
 structured logging - popular log collector/shipper format
In-Reply-To: <JIRA.17110.1681946398000@Atlassian.JIRA>
References: <JIRA.17110.1681946398000@Atlassian.JIRA>
 <JIRA.17110.1681946398046@yvo>
Message-ID: <mailman.2243.1686655381.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230613/0d88a9c9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230613/0d88a9c9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 375 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230613/0d88a9c9/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1156 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230613/0d88a9c9/attachment-0002.png>

From logback-dev at qos.ch  Tue Jun 13 16:27:54 2023
From: logback-dev at qos.ch (logback developers list)
Date: Tue, 13 Jun 2023 16:27:54 +0200
Subject: [logback-dev] Release of logback versions 1.3.8 and 1.4.8
Message-ID: <mailman.2244.1686666474.23762.logback-dev@qos.ch>


Hello all,

I am happy to announce the simultaneous release of logback
versions 1.3.8 and 1.4.8. Both versions require slf4j-api version
2.0.x or later.

In addition to fixing several outstanding bugs, these releases
add JsonEncoder which outputs logging events in Newline delimited
JSON (ndjson) format. For more details, please refer to the the
news page:

    http://logback.qos.ch/news.html

We thank the Sovereign Tech Fund for kindly championing these
releases.

    https://sovereigntechfund.de/en/

Why two simultaneous releases?

Given that downstream users are likely to depend on either Java EE (in
the javax namespace) or on Jakarta EE (in the jakarta namespace) in
their projects, it was deemed important for logback to support both EE
alternatives.

As such, logback 1.3.x supports Java EE whereas logback 1.4.x supports
Jakarta EE, otherwise the two versions are feature identical.

Both 1.3.x and 1.4.x series require the fluent-API introduced in SLF4J
2.0.x.

The 1.3.x series requires Java 8 at runtime. If you wish to build
logback from source, you will need Java 9.

The 1.4.x series requires Java 11 at build time and at runtime.

Groovy configuration:

Support for Groovy configuration was dropped for security reasons but
was recovered by Tucker Pelletier (virtualdogbert). See:

  https://github.com/virtualdogbert/logback-groovy-config

Benchmarks:

For benchmarking figures please see:

  http://logback.qos.ch/performance.html

Reproducible builds:

Recent logback releases are reproducible. This means that
checking out the code corresponding to the release version from
github and building it, will generate a binary identical to the
binary found on Maven central.

Donations and sponsorship

You can also support SLF4J/logback/reload4j projects via
donations and sponsorship. We thank our current supporters and
sponsors for their continued contributions and in particular The
Sovereign Tech Fund, Spotify R&D and Exoscale.

Sponsorship link: https://github.com/sponsors/qos-ch

Announcement mailing list:

You can receive SLF4J/logback/reload4j related announcements by
subscribing QOS.ch announce list, please visit the following URL.

   http://www.qos.ch/mailman/listinfo/announce

Enjoy,

-- 
Ceki Gülcü

From logback-dev at qos.ch  Thu Jun 15 22:21:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Thu, 15 Jun 2023 22:21:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1717) Reduce the memory footprint
 with GraalVM native image
In-Reply-To: <JIRA.17087.1678798963000@Atlassian.JIRA>
References: <JIRA.17087.1678798963000@Atlassian.JIRA>
 <JIRA.17087.1678798963569@yvo>
Message-ID: <mailman.2323.1686860461.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230615/da6438f5/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230615/da6438f5/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230615/da6438f5/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230615/da6438f5/attachment-0005.png>

From logback-dev at qos.ch  Fri Jun 16 21:47:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 16 Jun 2023 21:47:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1669) JmxConfigurator no more
	available in 1.4.0
In-Reply-To: <JIRA.16766.1661842522000@Atlassian.JIRA>
References: <JIRA.16766.1661842522000@Atlassian.JIRA>
 <JIRA.16766.1661842522105@yvo>
Message-ID: <mailman.2347.1686944821.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230616/3b54374d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230616/3b54374d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230616/3b54374d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2333 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230616/3b54374d/attachment-0002.png>

From logback-dev at qos.ch  Mon Jun 19 23:02:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Mon, 19 Jun 2023 23:02:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1717) Reduce the memory footprint
 with GraalVM native image
In-Reply-To: <JIRA.17087.1678798963000@Atlassian.JIRA>
References: <JIRA.17087.1678798963000@Atlassian.JIRA>
 <JIRA.17087.1678798963569@yvo>
Message-ID: <mailman.2402.1687208520.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230619/baa79c17/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230619/baa79c17/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230619/baa79c17/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230619/baa79c17/attachment-0005.png>

From logback-dev at qos.ch  Tue Jun 20 16:53:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Tue, 20 Jun 2023 16:53:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1746: insertFromJNDI fails
	in 1.4.6
In-Reply-To: <JIRA.17127.1687272122000@Atlassian.JIRA>
References: <JIRA.17127.1687272122000@Atlassian.JIRA>
 <JIRA.17127.1687272122116@yvo>
Message-ID: <mailman.2421.1687272780.23762.logback-dev@qos.ch>

logback / LOGBACK-1746 [Open]
insertFromJNDI fails in 1.4.6

==============================

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-1746

==============================
 Issue created
------------------------------

Richard Sand created this issue on 20/Jun/23 16:42

Summary:              insertFromJNDI fails in 1.4.6
Issue Type:           Bug
Affects Versions:     1.4.6
Assignee:             Logback dev list
Components:           logback-core
Created:              20/Jun/23 16:42
Priority:             Major
Reporter:             Richard Sand
Description:
  Similar to LOGBACK-1706, but I'm using 1.4.6 release but still encounter the issue. My configuration is unchanged, I simply changed the logback libraries from 1.2.6 to 1.4.6.
  
  My logback.xml:
  
   
  {{<configuration scan="true">}}
  {{  <insertFromJNDI env-entry-name="java:comp/env/appHome" as="appHome" />}}
  {{  <include file="${appHome}/conf/logback-ssorest.xml"/>}}
  {{  <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"> }}
  {{    <resetJUL>true</resetJUL> }}
  {{  </contextListener> }}
  {{</configuration>}}


==============================
 This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)


From logback-dev at qos.ch  Tue Jun 20 17:10:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Tue, 20 Jun 2023 17:10:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1747: Allow subclasses of
 LoggerContext to customize new Logger instances
In-Reply-To: <JIRA.17128.1687273116000@Atlassian.JIRA>
References: <JIRA.17128.1687273116000@Atlassian.JIRA>
 <JIRA.17128.1687273116077@yvo>
Message-ID: <mailman.2422.1687273800.23762.logback-dev@qos.ch>

logback / LOGBACK-1747 [Open]
Allow subclasses of LoggerContext to customize new Logger instances

==============================

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-1747

==============================
 Issue created
------------------------------

Richard Sand created this issue on 20/Jun/23 16:58

Summary:              Allow subclasses of LoggerContext to customize new Logger instances
Issue Type:           Improvement
Assignee:             Logback dev list
Components:           logback-classic
Created:              20/Jun/23 16:58
Priority:             Major
Reporter:             Richard Sand
Description:
  I've a use case where I am adapting Logback to work with a legacy product's proprietary log mechanism. I did this by creating a wrapper class around a {{Logger. }}But there is no hook to programmatically touch the {{Logger}} instances at creation-time.
  
  I submitted a pull request #635 ([https://github.com/qos-ch/logback/pull/635)] that addresses this by simply adding a method to {{LoggerContext }}that is invoked immediately after {{{}Logger.createChildByName(){}}}, which by default is a no-op but can be implemented by custom contexts.
  
   


==============================
 This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)


From logback-dev at qos.ch  Wed Jun 21 06:32:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 06:32:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1711) Deadlock when using Virtual
	Threads
In-Reply-To: <JIRA.16883.1670057556000@Atlassian.JIRA>
References: <JIRA.16883.1670057556000@Atlassian.JIRA>
 <JIRA.16883.1670057556467@yvo>
Message-ID: <mailman.2468.1687321921.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/0c4669f7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/0c4669f7/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/0c4669f7/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 799 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/0c4669f7/attachment-0002.png>

From logback-dev at qos.ch  Wed Jun 21 10:19:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 10:19:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1711) Deadlock when using Virtual
	Threads
In-Reply-To: <JIRA.16883.1670057556000@Atlassian.JIRA>
References: <JIRA.16883.1670057556000@Atlassian.JIRA>
 <JIRA.16883.1670057556467@yvo>
Message-ID: <mailman.2472.1687335540.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/a576808f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/a576808f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/a576808f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/a576808f/attachment-0005.png>

From logback-dev at qos.ch  Wed Jun 21 17:20:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 17:20:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1748: JsonEncoder: allow
 configuring to get formatted message in the json payload
In-Reply-To: <JIRA.17129.1687360117000@Atlassian.JIRA>
References: <JIRA.17129.1687360117000@Atlassian.JIRA>
 <JIRA.17129.1687360117209@yvo>
Message-ID: <mailman.2478.1687360800.23762.logback-dev@qos.ch>

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)


From logback-dev at qos.ch  Wed Jun 21 18:07:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 18:07:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1749: In the new
 JsonEncoder, the throwable's cause(s) are not included.
In-Reply-To: <JIRA.17131.1687362913000@Atlassian.JIRA>
References: <JIRA.17131.1687362913000@Atlassian.JIRA>
 <JIRA.17131.1687362913604@yvo>
Message-ID: <mailman.2483.1687363620.23762.logback-dev@qos.ch>

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)


From logback-dev at qos.ch  Wed Jun 21 19:33:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 19:33:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1750:
 Compressor.gzCompress() 'done' log msg is wrong - 'ZIP' is logged instead
 of 'GZ'
In-Reply-To: <JIRA.17132.1687368086000@Atlassian.JIRA>
References: <JIRA.17132.1687368086000@Atlassian.JIRA>
 <JIRA.17132.1687368086066@yvo>
Message-ID: <mailman.2491.1687368780.23762.logback-dev@qos.ch>

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)


From logback-dev at qos.ch  Wed Jun 21 19:33:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 19:33:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1751: StatusPrinter
 timestamp format should include date
In-Reply-To: <JIRA.17133.1687368361000@Atlassian.JIRA>
References: <JIRA.17133.1687368361000@Atlassian.JIRA>
 <JIRA.17133.1687368361391@yvo>
Message-ID: <mailman.2492.1687368780.23762.logback-dev@qos.ch>

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)


From logback-dev at qos.ch  Wed Jun 21 20:35:34 2023
From: logback-dev at qos.ch (logback developers list)
Date: Wed, 21 Jun 2023 14:35:34 -0400
Subject: [logback-dev] regarding LOGBACK-1746
Message-ID: <mailman.2497.1687372542.23762.logback-dev@qos.ch>

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 at 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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230621/8a454326/attachment.htm>

From logback-dev at qos.ch  Fri Jun 23 12:59:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 23 Jun 2023 12:59:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1752: SocketReceiver
 cannot deserialize events in OSGi
In-Reply-To: <JIRA.17134.1687517243000@Atlassian.JIRA>
References: <JIRA.17134.1687517243000@Atlassian.JIRA>
 <JIRA.17134.1687517243795@yvo>
Message-ID: <mailman.2550.1687517940.23762.logback-dev@qos.ch>

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)


From logback-dev at qos.ch  Fri Jun 23 14:37:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 23 Jun 2023 14:37:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1717) Reduce the memory footprint
 with GraalVM native image
In-Reply-To: <JIRA.17087.1678798963000@Atlassian.JIRA>
References: <JIRA.17087.1678798963000@Atlassian.JIRA>
 <JIRA.17087.1678798963569@yvo>
Message-ID: <mailman.2552.1687523820.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230623/a57d0ec3/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230623/a57d0ec3/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230623/a57d0ec3/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230623/a57d0ec3/attachment-0005.png>

From logback-dev at qos.ch  Mon Jun 26 17:38:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Mon, 26 Jun 2023 17:38:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] Updates for LOGBACK-1753: NPE in logback
 classic module (1.2.11)
In-Reply-To: <JIRA.17135.1687793210000@Atlassian.JIRA>
References: <JIRA.17135.1687793210000@Atlassian.JIRA>
 <JIRA.17135.1687793210571@yvo>
Message-ID: <mailman.2628.1687793880.23762.logback-dev@qos.ch>

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)


From logback-dev at qos.ch  Fri Jun 30 13:25:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 30 Jun 2023 13:25:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1753) NPE in logback classic module
	(1.2.11)
In-Reply-To: <JIRA.17135.1687793210000@Atlassian.JIRA>
References: <JIRA.17135.1687793210000@Atlassian.JIRA>
 <JIRA.17135.1687793210571@yvo>
Message-ID: <mailman.2713.1688124301.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/a441824f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/a441824f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/a441824f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/a441824f/attachment-0005.png>

From logback-dev at qos.ch  Fri Jun 30 13:25:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 30 Jun 2023 13:25:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1753) NPE in logback classic module
	(1.2.11)
In-Reply-To: <JIRA.17135.1687793210000@Atlassian.JIRA>
References: <JIRA.17135.1687793210000@Atlassian.JIRA>
 <JIRA.17135.1687793210571@yvo>
Message-ID: <mailman.2714.1688124301.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/8750719e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/8750719e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/8750719e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/8750719e/attachment-0005.png>

From logback-dev at qos.ch  Fri Jun 30 14:21:00 2023
From: logback-dev at qos.ch (logback developers list)
Date: Fri, 30 Jun 2023 14:21:00 +0200 (CEST)
Subject: [logback-dev] [JIRA] (LOGBACK-1750) Compressor.gzCompress() 'done'
 log msg is wrong - 'ZIP' is logged instead of 'GZ'
In-Reply-To: <JIRA.17132.1687368086000@Atlassian.JIRA>
References: <JIRA.17132.1687368086000@Atlassian.JIRA>
 <JIRA.17132.1687368086066@yvo>
Message-ID: <mailman.2717.1688127660.23762.logback-dev@qos.ch>

An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/c794cd46/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/c794cd46/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/c794cd46/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3408 bytes
Desc: not available
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20230630/c794cd46/attachment-0002.png>