warning message occasionally logged incorrectly when a client cursor is exhausted

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.2.1, 2.3.0
    • Affects Version/s: 2.2.0
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a ClientCursor::Pin is released and then destroyed, a "cursor not found in map" warning can occasionally be printed incorrectly. This happens when a client cursor is exhausted in process get more.

                      if ( warn )
                          OCCASIONALLY out() << "ClientCursor::find(): cursor not found in map " << id << " (ok after a drop)\n";
      

              Assignee:
              Aaron Staple (Inactive)
              Reporter:
              Aaron Staple (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: