// Simulate cluster failover (would require test environment setup)
    // ... trigger server failover ...
    
    // Verify that witness notification was received and handled
    assertTrue(listener.waitForNotification(30000));  // 30 second timeout
    
    // Verify file is still accessible after failover
    assertTrue(file.exists());
}

@Test

Calls are executed in one of two ways:

 * **Synchronous:** your thread blocks until the response is readable.

/**
 * SMB Witness Protocol client implementation as defined in MS-SWN specification.
 * Manages witness registrations, notifications, and heartbeats for cluster failover support.
 */
public class WitnessClient implements AutoCloseable {
    private static final Logger log = LoggerFactory.getLogger(WitnessClient.class);

    // Polling and backoff constants (in ms)

		data[i] = byte(rng.Int63() & 3)
	}
	failOnErr := func(err error) {
		if err != nil {
			logger.Fatal(errSelfTestFailure, "compress: error on self-test: %v", err)
		}
	}
	const skip = 2<<20 + 511
	r, _ := newS2CompressReader(bytes.NewBuffer(data), int64(len(data)), true)
	b, err := io.ReadAll(r)
	failOnErr(err)
	failOnErr(r.Close())
	// Decompression reader.

     * @return whether to enforce the use of secure negotiation.
     */
    boolean isRequireSecureNegotiate();

    /**
     * Enable port 139 failover
     *
     * Property {@code jcifs.smb.client.port139.enabled} (boolean, default false)
     *
     * @return whether to failover to legacy transport on port 139
     */
    boolean isPort139FailoverEnabled();

    /**
     *

    protected boolean forceExtendedSecurity = false;
    /** Whether to negotiate only SMB2 or higher protocols */
    protected boolean smb2OnlyNegotiation = false;
    /** Whether to failover to port 139 if port 445 fails */
    protected boolean port139FailoverEnabled = false;
    /** Whether to use NT SMB operations */
    protected boolean useNTSmbs = true;

requires a setting in the replication configuration called [replica modification sync](https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-replication-adds-support-two-way-replication/).

For active-active replication, automatic failover occurs on `GET/HEAD` operations if object or object version requested qualifies for replication and is missing on one site, but present on the other. This allows the applications to take full advantage of two-way replication even before the two sites...

                setSessionSetup(response);

                // Initialize multi-channel after successful session setup
                initializeMultiChannel();

                // Initialize witness support for fast failover
                initializeWitnessSupport();

                if (ex != null) {
                    throw ex;
                }
                return (T) (response != null ? response.getNextResponse() : null);

        poolSpy.logon(ctx, address);

        // Then: Should connect to IPC$ share
        verify(tree).connectLogon(ctx);
    }

    @Test
    @DisplayName("Should sort addresses by fail count and failover")
    void testFailoverWithFailCounts() throws Exception {
        // Given: Multiple addresses with different fail counts
        Address addr1 = mock(Address.class);

        /** Round-robin distribution */
        ROUND_ROBIN,
        /** Least connections */
        LEAST_CONNECTIONS,
        /** Random selection */
        RANDOM,
        /** Failover only (use primary until failure) */
        FAILOVER_ONLY
    }

    /**
     * Represents a group of channels for a single session.
     */
    public static class ChannelGroup {