When running, an error log is generated about every an hour:Caused by: java.net.ConnectException: Connection refused: connect #6141
-
Application ExceptionThen it would auto reconnect
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
Just so you know, both your RabbitMQ and Erlang versions are out-of-date and unsupported. It would be useful to know what RabbitMQ logs at the same time that this exception occurs. Please provide that. My guess is that you have a network device between your application and RabbitMQ that is closing the TCP connection. |
Beta Was this translation helpful? Give feedback.
-
Something tries to connect using Spring AMQP and that connection fails. We recommend a specific methodology for troubleshooting connectivity issues effectively. |
Beta Was this translation helpful? Give feedback.
-
We have explained the methodoglogy and what the "unexpected TCP connection closure" message means. We won't be able to help you identify why your application may fail to connect, or what clients |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Finally, RabbitMQ 3.8.1 is a fine version from three years ago that is 34 patch releases behind in an out-of-support release series. Consider upgrading. |
Beta Was this translation helpful? Give feedback.
We have explained the methodoglogy and what the "unexpected TCP connection closure" message means.
We won't be able to help you identify why your application may fail to connect, or what clients
abruptly close connections or why. Please use the methodology document to narrow down what's
going on in your system.