spring-cloud / spring-cloud/spring-cloud-commons
Thread safety of @ConfigurationProperties beans when refreshing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Describe the bug
We use Spring Cloud Config service and we noticed that from time to time we are getting exceptions like ConcurrentModificationException when accessing some collection types from the properties. Are @ConfigurationProperties bean supposed to be thread safe? If not what is the recommended way to make them thread safe?
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
No source file or test is named. Start by tracing how @ConfigurationProperties beans are refreshed through Spring Cloud Config, then look for a reproducible concurrent collection access case. Done means establishing the supported thread-safety behavior and recording a maintainer-confirmed recommendation, with a focused test only if the behavior is considered defective.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100