emptyIterator.next();
                count++;
                if (count > 10)
                    break; // Safety check
            }
            assertEquals(0, count, "No iterations should occur for empty iterator");
        }, "EmptyIterator should work with manual iteration");
    }

    @Test
    @DisplayName("EmptyIterator should handle concurrent access safely")

 * <p>This pattern ensures the following:
 *
 * <ul>
 *   <li>Each {@code Closeable} resource that is successfully registered will be closed later.
 *   <li>If a {@code Throwable} is thrown in the try block, no exceptions that occur when attempting
 *       to close resources will be thrown from the finally block. The throwable from the try block
 *       will be thrown.

 * specified the JVM flag {@code -XX:+DisableExplicitGC}. But in practice, it works very well for
 * ordinary tests.
 *
 * <p>Failure of the expected event to occur within an implementation-defined "reasonable" time
 * period or an interrupt while waiting for the expected event will result in a {@link
 * RuntimeException}.
 *
 * <p>Here's an example that tests a {@code finalize} method:

 * specified the JVM flag {@code -XX:+DisableExplicitGC}. But in practice, it works very well for
 * ordinary tests.
 *
 * <p>Failure of the expected event to occur within an implementation-defined "reasonable" time
 * period or an interrupt while waiting for the expected event will result in a {@link
 * RuntimeException}.
 *
 * <p>Here's an example that tests a {@code finalize} method:

     * @throws IOException if an I/O error occurs
     */
    public static void store(final OutputStream out, final String header) throws IOException {
        prp.store(out, header);
    }

    /**
     * List the properties in the <code>Config</code>.
     *
     * @param out the print stream to write the properties to
     * @throws IOException if an I/O error occurs
     */

    enableTlsWithTunnel()
    server.protocols = Arrays.asList(Protocol.HTTP_2, Protocol.HTTP_1_1)
    timeToFirstByte()
  }

  /**
   * Test to confirm that events are reported at the time they occur and no earlier and no later.
   * This inserts a bunch of synthetic 250 ms delays into both client and server and confirms that
   * the same delays make it back into the events.
   *

                 * SMB_COM_SESSION_SETUP_ANDX from having it's uid set to an
                 * old value when the session is re-established. Otherwise a
                 * "The parameter is incorrect" error can occur.
                 */
                uid = 0;

                do {
                    switch (state) {
                    case 10: /* NTLM */

                }
            } catch (final SmbException e) {
                if (e.getNtStatus() == NtStatus.NT_STATUS_INVALID_PARAMETER) {
                    // Silently ignore invalid parameter errors - these may occur with certain server configurations
                    if (log.isDebugEnabled()) {
                        log.debug("Invalid parameter error.", e);
                    }
                    return;
                }

        // This test verifies that ProtwordsUpdater constructor properly handles exceptions
        // The actual exception handling is tested by ensuring the updater can be created
        // and properly closed even when errors might occur

        protwordsFile.reload(null);

        // Test normal creation and cleanup of ProtwordsUpdater
        ProtwordsItem testItem = new ProtwordsItem(0, "testWord");

import jcifs.internal.smb1.trans.nt.NtTransQuerySecurityDesc;
import jcifs.util.transport.TransportException;

/**
 * This class encapsulates the logic for switching tree connections
 *
 * Switching trees can occur either when the tree has been disconnected by failure or idle-timeout - as well as on
 * DFS referrals.
 *
 * @author mbechler
 *
 */
class SmbTreeConnection implements AutoCloseable {