JAVA-6302Investigating
Server monitor handshake write has no effective timeout — MongoClient never recovers after frozen-flow TCP disruption (async transports)
h3. Issue + Relevant Info Reported via MongoDB Support case. After a transient network disruption to the cluster, affected {{MongoClient}} instances *never recover* even once the cluster is fully reachable again: every replica-set member stays {{type=UNKNOWN, state=CONNECTING}} indefinitely, and only a JVM restart restores connectivity. Root cause (confirmed with the Java driver team on Slack): the server-monitor handshake *write* leg has no effective timeout. This violates the CSOT spec,