spring-projects / spring-projects/spring-boot
Provide a configuration option to disable transferring logging.* properties from the environment to system properties
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Hi,
We have a Spring boot application deployed into a tomcat instance. A tomcat instance can contain multiple webapp instances.
We noticed that Spring Boot logger system was setting system properties using System.setProperty in LoggingSystemProperties. This is very bad in our case since a system property is global to the JVM and therefore to all deployed web applications.
This looks like a major bug to us.
Is there at least a way to disable LoggingApplicationListener?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading LoggingSystemProperties and LoggingApplicationListener, focusing on how logging.* environment properties are transferred with System.setProperty. Trace the existing logging initialization path and determine where a configuration option could control that transfer. Done means applications can disable the transfer so logging properties are not made global to the JVM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100