[JAVA-4483] Fix and disable ServerDiscoveryAndMonitoringProseTests.testConnectionPoolManagement Created: 07/Feb/22  Updated: 28/Oct/23  Resolved: 08/Feb/22

Status: Closed
Project: Java Driver
Component/s: Test Failure
Affects Version/s: None
Fix Version/s: 4.5.0

Type: Improvement Priority: Minor - P4
Reporter: Valentin Kavalenka Assignee: Valentin Kavalenka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes JAVA-4484 Enable ServerDiscoveryAndMonitoringPr... Blocked
is caused by JAVA-3928 Connection pool paused state Closed
Related
related to DRIVERS-2194 Clarify the order between server moni... Backlog
Backwards Compatibility: Fully Compatible
Documentation Changes: Not Needed

 Description   

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.



 Comments   
Comment by Githook User [ 08/Feb/22 ]

Author:

{'name': 'Valentin Kovalenko', 'email': 'valentin.kovalenko@mongodb.com', 'username': 'stIncMale'}

Message: Fix ServerDiscoveryAndMonitoringProseTests.testConnectionPoolManagement and disable it (#873)

JAVA-4483
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/e557fc465d9fc7fc122cfcbe4f8b397bf0f475f7

Generated at Thu Feb 08 09:02:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.