RabbitMQ 3.8.5 with com.rabbitmq.amqp-client:5.17.0 throw connection refused exception

[Rasoul Firoz]

I'm using RabbitMQ 3.8.5 with client 5.17.0 using correct username and password, but still the connection is refused. Any help is appreciated. Here is the log

2023-07-12 14:41:59.996 [AMQP Connection 40.78.134.233:5672] |WARN  |c.r.c.impl.ForgivingExceptionHandler [ForgivingExceptionHandler.java:115] An unexpected connection driver error occurred (Exception message: Connection reset)  
2023-07-12 14:42:00.002 [main] |ERROR |com.nuance.config.AMQPConfig [AMQPConfig.java:52] Exception occured when creating connection/channel to rabbitmq. com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.\r\n   at com.rabbitmq.client.impl.AMQConnection.start(AMQConnection.java:385)\

[Gavin M. Roy]

Per the error, what does the broker log file say?

> For details see the broker logfile

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/4677b489-afaa-44cc-a7af-a50a395e43e4n%40googlegroups.com.

[Ethan Tun]

Hi, I am having similar issue with com.rabbitmq:amqp-client:5.13.1.
The broker log file says 

2023-08-18 18:07:47.749 [warning] <0.8643.311> closing AMQP connection <0.8643.311> (10.148.104.107:16188 -> 10.148.107.3:5672 - connectionFactory#1952f6e3:2...... client unexpectedly closed TCP connection
Whenever we see the error, a largo portion of messages are lost. Could you please help?

[Ethan Tun]

also the rabbit server version is  3.7.17

[Michal Kuratczyk]

1. Your issue doesn't look like the original issue. Start a new thread if needed.

2. RabbitMQ 3.7 has been out of support for 3 years, so do not expect RabbitMQ team support until you upgrade.

3. The log message just says that the client connection was abruptly terminated. There's not much more RabbitMQ can say/do about it.

Debug your client app / network to understand why they terminate the connection.

As for the data loss, most likely either the messages aren't really lost or you are not using publish confirms / acknowledgments.

If you want to report a data loss issue, provide an executable way of reproducing the problem (https://perftest.rabbitmq.com/ is great for this)

against a supported RabbitMQ version.

Best,

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/2df03d5d-821d-402c-9238-0ce2812affcfn%40googlegroups.com.

--

Michał

RabbitMQ team

[Ethan Tun]

Thanks for your response Michal.

I just figured out the root cause. It was because we are using classic AWS loadbalancers between client and server that will scale and change ip during high message load, which caused the connection reset issue. According to some stackoverflow discussion, it is recommended to use Network load balancers which I am currently testing now.

Thanks