[JAVA-4856] Ensure ObjectId uniqueness when using GraalVM Created: 24/Jan/23 Updated: 28/Oct/23 Resolved: 09/Feb/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Native Images |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kai Orend | Assignee: | Maxim Katcharov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | graalvm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||||||
| Description |
|
A customer stumbled over duplicate errors caused by duplicate ObjectIds which were generated on different Servers, while using GraalVM. It looked like the SecureRandom implementation did generate deterministic values rather than non deterministic ones. Add a native-image.properties to bson and include Args = --initialize-at-run-time=org.bson.types.ObjectId |
| Comments |
| Comment by Githook User [ 06/Feb/23 ] |
|
Author: {'name': 'Maxim Katcharov', 'email': 'maxim.katcharov@mongodb.com', 'username': 'katcharov'}Message: Initialize ObjectId, ClientMetadataHelper at runtime, GraalVM (#1078)
|
| Comment by Jeffrey Yemin [ 24/Jan/23 ] |
|
References:
We should check with Quarkus maintainers to see whether this is a problem for every Quarkus user. |