## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used (`minio --version`):
* Server setup and configuration:

MinIO server allows to throttle incoming requests:

- limit the number of active requests allowed across the cluster
- limit the wait duration for each request in the queue

These values are enabled using server's configuration or environment variables.

## Examples

### Configuring connection limit

TFCI_BAZEL_COMMON_ARGS="--repo_env=HERMETIC_PYTHON_VERSION=$TFCI_PYTHON_VERSION --repo_env=USE_PYWRAP_RULES=True --config=windows_x86_cpu_2022"

# For RBE, we explicitly set invalid paths to force the auto-configuration to fail.
TFCI_BAZEL_VC="C:/RBE_ISOLATED_INVALID_PATH"
TFCI_BAZEL_LLVM="C:/RBE_ISOLATED_INVALID_PATH"
TFCI_BAZEL_SH="C:/tools/msys64/usr/bin/bash.exe"
TFCI_USE_CLANG_CL=0

  virtual ~ImmediateExecutionDistributedManager() {}

  // Set up distributed execution environment on local and remote tasks.
  // When `reset_context` is true, initialize new cluster context state based
  // on cluster configurations provided in `server_def`; otherwise, update
  // existing context state with the provided `server_def`. Contexts created
  // on remote tasks will be considered stale and garbage collected after

          <description>Default plugin information to be made available for reference by projects
            derived from this one. This plugin configuration will not be resolved or bound to the
            lifecycle unless referenced. Any local configuration for a given plugin will override
            the plugin's entire definition here.</description>
          <association>
            <type>PluginManagement</type>

        }
    }

    /**
     * Test typical server configuration scenario
     */
    @Test
    @DisplayName("Test typical server configuration scenario")
    public void testTypicalServerConfiguration() {
        // Given - typical SMB server configuration
        serverData.sflags = (byte) 0x98;
        serverData.sflags2 = 0xC853; // Unicode, extended security, etc.

                        oldArchives.from(v1Jar)
                        oldClasspath.from(v1.configurations.named("runtimeClasspath"), v1Jar)

                        newArchives.from(v2Jar)
                        newClasspath.from(v2.configurations.named("runtimeClasspath"), v2Jar)

                        onlyModified.set(false)

Installing the Chart Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...

Installing the Chart Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...

Installing the Chart Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...