Closed siaavush closed 1 month ago
There appears to be a NamedContributors
implementation in your application that is not thread-safe and I would guess that a request to the health endpoint is being made on one thread while another thread is manipulating the contents of the NamedContributors
instance. Unfortunately, a stack trace alone isn't enough to identify the instance. NamedContributors
is an interface and we can't tell which implementation, be it one from Boot's codebase or from elsewhere, is affected. Can you please provide a minimal sample that reproduces the problem?
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Hey, @wilkinsona it's a good clue that it's an interface and implementation is being done by third-party starters, will dig deeper to this and give an update if I find the root cause. For now I think we can close the issue since its not a Spring Boot issue.
For those who are interested they can follow the topic on this issue on Spring cloud solace binder repo: https://github.com/SolaceProducts/solace-spring-cloud/issues/323
Bug report
Spring boot version: "3.2.4" Language: Kotlin Virtual threads are enabled
Description: ConcurrentModificationException happens occasionally in our backend service with no obvious reason.
Stack trace: