Ensure ObjectId uniqueness when using GraalVM

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: GraalVM
    • None
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      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
      Refs: https://www.graalvm.org/latest/reference-manual/native-image/dynamic-features/JCASecurityServices/#securerandom

              Assignee:
              Maxim Katcharov
              Reporter:
              Kai Orend
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: