*
     * @return an {@link Optional} containing true if the build should never fail, false if it should fail normally, or empty if not specified
     */
    @Nonnull
    Optional<Boolean> failNever();

    /**
     * Indicates whether Maven should resume from the last failed project in a previous build.
     *

    @Mock
    private SmbTransport mockNewTransport;

    @Mock
    private CommonServerMessageBlock mockOperation;

    private ChannelFailover failover;
    private ChannelInfo failedChannel;

    @BeforeEach
    void setUp() throws UnknownHostException {
        failover = new ChannelFailover(mockChannelManager);

        InetAddress addr = InetAddress.getByName("192.168.1.100");

    }

    /**
     * State tracking for channel failover
     */
    public static class FailoverState {

        private final String channelId;
        private final long failureTime;
        private int retryCount;
        private long nextRetryTime;

        /**
         * Create failover state
         *
         * @param channelId channel identifier
         */

        assertEquals(1024, channel.getBytesSent());
        assertTrue(channel.getLastActivityTime() > 0);
    }

    @Test
    void testChannelFailover() throws Exception {
        // Test failover mechanism
        ChannelFailover failover = new ChannelFailover(channelManager);

        // Create a channel
        InetAddress addr = InetAddress.getByName("192.168.1.100");

## 1. Overview

SMB3 Multi-Channel enables the use of multiple network connections between client and server, providing increased throughput, network fault tolerance, and automatic failover capabilities. This feature aggregates bandwidth across multiple NICs and provides seamless failover when network paths fail.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 3.2.4.23**: FSCTL_QUERY_NETWORK_INTERFACE_INFO

- [ ] Create resource monitoring
- [ ] Implement automatic re-registration
- [ ] Add cluster node tracking
- [ ] Create failover coordination

#### 6.3 Integration Points
- Integrate with `CIFSContext` for witness support
- Modify `SmbTransport` for failover handling
- Update `DfsResolver` for witness-aware resolution

---

## Implementation Dependencies

```mermaid
graph TD

 */
public enum WitnessEventType {
    /**
     * Resource state changed - general resource state modification
     */
    RESOURCE_CHANGE(1),

    /**
     * Client should move to different node - directed failover
     */
    CLIENT_MOVE(2),

    /**
     * Share moved to different node - share mobility event
     */
    SHARE_MOVE(3),

    /**
     * IP address changed - network configuration change
     */

    private final List<NetworkInterfaceInfo> remoteInterfaces;
    private final ScheduledExecutorService scheduler;
    private final ChannelLoadBalancer loadBalancer;
    private final ChannelFailover failover;

    private volatile boolean multiChannelEnabled;
    private final int maxChannels;
    private final AtomicInteger channelCounter;

    /**
     * Create channel manager
     *

    
    // 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.