Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-1163

Unsafe setting of firstChangeNumber/lastChangeNumber when the database is empty

    XMLWordPrintable

Details

    • Bug
    • Status: Done
    • Minor
    • Resolution: Fixed
    • 2.6.0
    • 2.6.1
    • replication
    • None

    Description

      This code in ReplicationServer.java is unsafe, as lastGeneratedDraftCN might be altered in parallel.

      ReplicationServer.java
      // The database was empty, just keep increasing numbers since last time
      // we generated one DraftCN.
      firstDraftCN += lastGeneratedDraftCN;
      lastDraftCN += lastGeneratedDraftCN;
      

      The code has been fixed on the trunk already.

      Attachments

        Activity

          People

            cjr Chris Ridd
            cjr Chris Ridd
            Chris Ridd Chris Ridd
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: