Change test expectation

Garbage in the SASL frame can also trigger a timeout because the broker
closes the connection before the client can throw the SASL error.

Author: acogoluegnes

src/main/java/com/rabbitmq/stream/impl/Client.java

@@ -2877,7 +2877,7 @@ public void run() {
         try {
           this.message.release();
         } catch (Exception e) {
-          e.printStackTrace();
+          LOGGER.info("Error while releasing buffer after connection closing: {}", e.getMessage());
         }
       } else {
         this.frameHandler.handle(this.client, this.frameSize, this.ctx, this.message);

src/test/java/com/rabbitmq/stream/impl/AuthenticationTest.java

@@ -23,6 +23,7 @@
 import com.rabbitmq.stream.StreamException;
 import com.rabbitmq.stream.sasl.*;
 import java.nio.charset.StandardCharsets;
+import java.time.Duration;
 import java.util.UUID;
 import org.junit.jupiter.api.Test;
 import org.junit.jupiter.api.extension.ExtendWith;
@@ -87,6 +88,7 @@ void authenticateShouldFailWhenSendingGarbageToSaslChallenge() {
     try {
       cf.get(
           new Client.ClientParameters()
+              .rpcTimeout(Duration.ofSeconds(1))
               .saslConfiguration(
                   mechanisms ->
                       new SaslMechanism() {
@@ -102,7 +104,10 @@ public byte[] handleChallenge(
                         }
                       }));
     } catch (StreamException e) {
-      assertThat(e.getMessage()).contains(String.valueOf(Constants.RESPONSE_CODE_SASL_ERROR));
+      // there can be a timeout because the connection gets closed before returning the error
+      assertThat(e.getMessage())
+          .containsAnyOf(
+              String.valueOf(Constants.RESPONSE_CODE_SASL_ERROR), "Could not get response in");
     }
   }