6ec264252b
Prior to this commit, the `ConcurrentReferenceHashMap#Segment` would recalculate its element count during the restructure phase by subtracting the number of polled elements from the queue to the current count. Later, the newly restructured `references` array would only contain references that 1) are not in the set of elements to purge and 2) that hold a non-null value. The issues with this approach are multiple. The newly calculated count is only an estimate, as some situations can make it invalid, even temporarily. * since we initially collected all elements to be purged from the queue, the GC might have collected new values. This means that we might filter out more references that we initially intended to * because the restructure operation re-creates new references for all elements in the original array, we might later get references from the queue that are not in the array anymore. This could lead to "duplicate" removals for the same value Because several methods in the Segment class have special no-op behavior when `count == 0`, an invalid count can lead to keys appearing missing when they are actually still present. In some scenarios, this can decrease the performance of the cache since values need to be recalculated. This commit fixes this inconsistency count issue by first using an estimate in order to decide whether the array needs a resize and then by counting the actual numbers of elements inserted in the restructured array as the new count. Fixes gh-31373
Spring Framework 
This is the home of the Spring Framework: the foundation for all Spring projects. Collectively the Spring Framework and the family of Spring projects are often referred to simply as "Spring".
Spring provides everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures. Please read the Overview section as reference for a more complete introduction.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.
Access to Binaries
For access to artifacts or a distribution zip, see the Spring Framework Artifacts wiki page.
Documentation
The Spring Framework maintains reference documentation (published and source), GitHub wiki pages, and an API reference. There are also guides and tutorials across Spring projects.
Micro-Benchmarks
See the Micro-Benchmarks wiki page.
Build from Source
See the Build from Source wiki page and the CONTRIBUTING.md file.
Continuous Integration Builds
Information regarding CI builds can be found in the Spring Framework Concourse pipeline documentation.
Stay in Touch
Follow @SpringCentral, @SpringFramework, and its team members on Twitter. In-depth articles can be found at The Spring Blog, and releases are announced via our news feed.
License
The Spring Framework is released under version 2.0 of the Apache License.