Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-3099

SDAM Monitoring crashes

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.6.4
    • Component/s: None
    • Labels:

      Node version: 14.15.4
      Database version: 4.4
      Driver version: 3.6.4

      {
          "ismaster" : true,
          "topologyVersion" : {
              "processId" : ObjectId("601d6699d2ee9c07013b73dd"),
              "counter" : NumberLong(0)
          },
          "maxBsonObjectSize" : 16777216,
          "maxMessageSizeBytes" : 48000000,
          "maxWriteBatchSize" : 100000,
          "localTime" : ISODate("2021-02-05T17:47:45.887Z"),
          "logicalSessionTimeoutMinutes" : 30,
          "connectionId" : 18226,
          "minWireVersion" : 0,
          "maxWireVersion" : 9,
          "readOnly" : false,
          "ok" : 1.0
      }
      

       

      We have a test suite that runs in mocha in continuous mode, against a running MongoDB instance.

      After the first runs succeeds, MongoDB then crashes with the following error:

      TypeError: Cannot read property 'wake' of null
       at Timeout.setTimeout (/Volumes/MacData/git/work/reedsy/reedsy-editor/node_modules/mongoose/node_modules/mongodb/lib/core/sdam/monitor.js:309:33)
       at ontimeout (timers.js:436:11)
       at tryOnTimeout (timers.js:300:5)
       at listOnTimeout (timers.js:263:5)
       at Timer.processTimers (timers.js:223:10)

      Before each test, we connect to the database, and drop the whole database. After each test, we disconnect.

      I'm not familiar with the SDAM events (I'd also be happy with just disabling this class!), but potentially provided with more context as to when this error can happen, I can try to make a minimal example.

            Assignee:
            Unassigned Unassigned
            Reporter:
            alec@reedys.com Alec Gibson
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: