throw new RuntimeException(e);
            }
        }, "Multiple close operations should not cause issues");

        // Verify iterator still works after multiple closes
        assertFalse(emptyIterator.hasNext(), "Iterator should still work after multiple closes");
        assertNull(emptyIterator.next(), "Iterator should still return null after multiple closes");
    }

    @Test

        ("/required?foo=bar", 200, {"foo": "bar"}),
        ("/required", 422, foo_is_missing),
        ("/required?foo=", 422, foo_is_short),
        ("/multiple?foo=bar", 200, {"foo": "bar"}),
        ("/multiple", 422, foo_is_missing),
        ("/multiple?foo=", 422, foo_is_short),
        ("/unrelated?foo=bar", 200, {"foo": "bar"}),
        ("/unrelated", 422, foo_is_missing),
    ],
)

        String[] permissions = fessUserBean.getPermissions();
        assertEquals(1, permissions.length);
        assertEquals("read", permissions[0]);

        // Test with multiple permissions
        testUser.setPermissions(new String[] { "read", "write", "delete" });
        permissions = fessUserBean.getPermissions();
        assertEquals(3, permissions.length);

        // Then
        assertNotNull(transportPool, "Transport pool should not be null");
        assertSame(transportPool, context.getTransportPool(), "Should return same instance on multiple calls");
    }

    @Test
    @DisplayName("getConfig should return the provided configuration")
    void testGetConfig() {
        // When
        Configuration config = context.getConfig();

But in many cases, you will want to run several worker processes at the same time.

### Multiple Processes - Workers { #multiple-processes-workers }

### One Load Balancer - Multiple Worker Containers { #one-load-balancer-multiple-worker-containers }

When working with **Kubernetes** or similar distributed container management systems, using their internal networking mechanisms would allow the single **load balancer** that is listening on the main **port** to transmit communication (requests) to possibly **multiple containers** running your app.

## Query parameter list / multiple values { #query-parameter-list-multiple-values }

When you define a query parameter explicitly with `Query` you can also declare it to receive a list of values, or said in another way, to receive multiple values.

For example, to declare a query parameter `q` that can appear multiple times in the URL, you can write:

    @Nested
    @DisplayName("Edge Cases and Error Handling")
    class EdgeCaseTests {

        @Test
        @DisplayName("Should handle multiple operations correctly")
        void testMultipleOperations() throws NdrException {
            // Given: NdrShort that will be used multiple times
            NdrShort ndrShort = new NdrShort(50);
            NdrBuffer buffer1 = mock(NdrBuffer.class);

    void testGetRequest() {
        // Verify getRequest returns the exact same instance
        SmbNegotiationRequest request = negotiation.getRequest();
        assertSame(mockRequest, request);

        // Verify multiple calls return the same instance
        assertSame(request, negotiation.getRequest());
    }

    @Test
    @DisplayName("getResponse should return the same response instance")
    void testGetResponse() {

	}

	keys := store.List()
	if len(keys) != 6 {
		// 1 multiple + 5 single PUTs
		t.Fatalf("expected len(keys)=6, but found %d", len(keys))
	}

	var resultItems []TestItem
	for _, key := range keys {
		if key.ItemCount > 1 {
			items, err := store.GetMultiple(key)
			if err != nil {
				t.Fatalf("unable to get multiple items; %v", err)
			}
			resultItems = append(resultItems, items...)