handle.close();

        // Assert
        // sendrecv for open is called once
        verify(mockDcerpcHandle, times(1)).sendrecv(any(MsrpcSamrOpenDomain.class));
        // sendrecv for close is called only once, even if close() is called multiple times
        verify(mockDcerpcHandle, times(1)).sendrecv(any(MsrpcSamrCloseHandle.class));
    }

    @Test
    void close_shouldThrowSmbExceptionOnRpcError() throws IOException {

    public void test_processWithNullResponseData() {
        // Test process method with null ResponseData
        NullResponseProcessor processor = new NullResponseProcessor();

        // Execute - should not throw any exception even with null
        processor.process(null);
    }

    public void test_processWithEmptyResponseData() {
        // Test process method with empty ResponseData

   * have started execution. This applies also to tasks given to {@code invokeAll} or {@code
   * invokeAny} which are pending serial execution, even the subset of the tasks that have not yet
   * started execution. It is unclear from the {@code ExecutorService} specification if these should

   *
   * <p>It's acceptable for the underlying table to contain null keys, and even null values provided
   * that the function is capable of accepting null input. The transformed table might contain null
   * values, if the function sometimes gives a null result.
   *
   * <p>The returned table is not thread-safe or serializable, even if the underlying table is.
   *

        Arrays.fill(buffer, 0, 24, (byte) 0xAA);

        // Decode with len = 24 (minimum valid)
        int bytesConsumed = response.decode(buffer, 0, 24);

        // Verify - should consume 28 bytes even though len is 24
        assertEquals(28, bytesConsumed, "Should consume 28 bytes");

        byte[] resumeKey = response.getResumeKey();
        assertNotNull(resumeKey, "Resume key should not be null");

            assertEquals("Braces should be balanced", openBraces, closeBraces);
        }
    }

    /**
     * Test that InputStream is properly closed even when exception occurs.
     * Verifies try-with-resources cleanup behavior.
     */
    @Test
    public void testResourceLoading_exceptionHandling() {
        try {

import org.dbflute.utflute.core.PlainTestCase;

/**
 * Test class to verify proper resource management in Extractor implementations.
 * This test ensures that resources are properly closed even when exceptions occur.
 */
public class ExtractorResourceManagementTest extends PlainTestCase {
    private static final Logger logger = LogManager.getLogger(ExtractorResourceManagementTest.class);

 * version 2.1 of the License, or (at your option) any later version.
 *
 * This library is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public

    expectedEvents += RequestHeadersStart::class
    expectedEvents += RequestHeadersEnd::class
    expectedEvents += RequestBodyStart::class
    // ... but we can read the response even after writing the request fails.
    expectedEvents += RequestFailed::class
    expectedEvents += ResponseHeadersStart::class
    expectedEvents += ResponseHeadersEnd::class
    expectedEvents += FollowUpDecision::class

 * invoke methods, they invoke methods on the {@code ForwardingSortedMultiset}.
 *
 * <p>The {@code standard} methods and any collection views they return are not guaranteed to be
 * thread-safe, even when all of the methods that they depend on are thread-safe.
 *
 * @author Louis Wasserman
 * @since 15.0
 */
@GwtCompatible
public abstract class ForwardingSortedMultiset<E extends @Nullable Object>