Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4483

Fix and disable ServerDiscoveryAndMonitoringProseTests.testConnectionPoolManagement

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 4.5.0
    • Affects Version/s: None
    • Component/s: Test Failure
    • None
    • Fully Compatible
    • Not Needed

      ServerDiscoveryAndMonitoringProseTests.testConnectionPoolManagement started failing like this after implementing JAVA-4449. This is a manifestation of a bug in the test, because the test relies on the assumption that ServerHeartbeatFailedEvent is ordered before ConnectionPoolClearedEvent that is caused by it. The corresponding test scenario in the spec does not make the same assumption: it does not expect any order between events in the phrase "Verify that a ServerHeartbeatFailedEvent and a ConnectionPoolClearedEvent (CMAP) are emitted."

      Another problem is that JAVA-4449 actually eliminated ordering relations that are expected by the aforementioned test. However, neither SDAM nor CMAP specs require such ordering relations outside of the test. I filed DRIVERS-2194, and for now we need to disable the test.

            valentin.kovalenko@mongodb.com Valentin Kavalenka
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            0 Vote for this issue
            1 Start watching this issue