This might affect 2.x, though it’s largely in the Spring environment property source. Given the application lifecycle there, Spring doesn’t seem to remove its own closed property sources at shutdown, hence the exception. The issue was only reported against Spring 3, though.
> On Jan 10, 2024, at 4:04 AM, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi Ralph, > > On Tue, 9 Jan 2024 at 22:45, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> >> FYI - in >> https://github.com/spring-projects/spring-boot/issues/33450#issuecomment-1883014368 >> has confirmed that Log4j 3.0.0-beta1 now works correctly with Spring 3.x. > > Are you planning to backport that patch or is it specific to 3.x? > > Piotr
