-
Notifications
You must be signed in to change notification settings - Fork 910
ConcurrentModificationException in MetaTableSchemaCache #5955
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@musketyr I understand it's hard to reproduce, but can you share a code example showing how you're using the Enhanced Client? We want to have a better picture of the use case. |
@debora-ito you can get better picture by checking https://github.com/agorapulse/micronaut-aws-sdk repository. this particular issue happens when the test is trying to parallelize loading of the CSV files into DynamoDB. the test within the repository is rather simple but in our codebase we are loading multiple CSV files in parallel at once to minimize the integration test start up time. This triggers transitively parallel lookup for the database service for given entity type and parallel calls to |
@musketyr can i work on this issue? |
It's not really up to me to decide 😀 but I hope that PRs are always welcomed. |
Describe the bug
When
MetaTableSchemaCache
is accessed concurrently, it leads toMetaTableSchemaCache ConcurrentModificationException
.Regression Issue
Expected Behavior
MetaTableSchemaCache
is thread safe.Current Behavior
MetaTableSchemaCache
is not thread safe and may causeConcurrentModificationException
.Reproduction Steps
The issue is random and difficult to reproduce but the solution is obvious (see below).
Possible Solution
Replace
with
Additional Information/Context
No response
AWS Java SDK version used
2.29.7
JDK version used
Azul Zulu OpenJDK 64-Bit Server VM 21.0.6+7-LTS (mixed mode, emulated-client, sharing)
Operating System and version
macOS 15.0.1 (aarch64)
The text was updated successfully, but these errors were encountered: