SpringCloud学习过程中遇到错误 Rabbit health check failed

解决方案在最下方

错误信息

2021-05-10 15:42:56.330  WARN 31692 --- [)-192.168.232.1] o.s.b.a.amqp.RabbitHealthIndicator       : Rabbit health check failedorg.springframework.amqp.AmqpConnectException: java.net.ConnectException: Connection refused: connectat org.springframework.amqp.rabbit.support.RabbitExceptionTranslator.convertRabbitAccessException(RabbitExceptionTranslator.java:61) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.createBareConnection(AbstractConnectionFactory.java:524) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.createConnection(CachingConnectionFactory.java:751) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils.createConnection(ConnectionFactoryUtils.java:214) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.core.RabbitTemplate.doExecute(RabbitTemplate.java:2089) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.core.RabbitTemplate.execute(RabbitTemplate.java:2062) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.core.RabbitTemplate.execute(RabbitTemplate.java:2042) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.boot.actuate.amqp.RabbitHealthIndicator.getVersion(RabbitHealthIndicator.java:49) ~[spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.amqp.RabbitHealthIndicator.doHealthCheck(RabbitHealthIndicator.java:44) ~[spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.AbstractHealthIndicator.health(AbstractHealthIndicator.java:82) ~[spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthIndicator.getHealth(HealthIndicator.java:37) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpoint.getHealth(HealthEndpoint.java:71) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpoint.getHealth(HealthEndpoint.java:39) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpointSupport.getContribution(HealthEndpointSupport.java:99) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpointSupport.getAggregateHealth(HealthEndpointSupport.java:110) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpointSupport.getContribution(HealthEndpointSupport.java:96) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpointSupport.getHealth(HealthEndpointSupport.java:74) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpointSupport.getHealth(HealthEndpointSupport.java:61) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpoint.health(HealthEndpoint.java:65) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.health.HealthEndpoint.health(HealthEndpoint.java:55) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_251]at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_251]at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_251]at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_251]at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) [spring-core-5.2.8.RELEASE.jar:5.2.8.RELEASE]at org.springframework.boot.actuate.endpoint.invoke.reflect.ReflectiveOperationInvoker.invoke(ReflectiveOperationInvoker.java:77) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.endpoint.annotation.AbstractDiscoveredOperation.invoke(AbstractDiscoveredOperation.java:60) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.endpoint.jmx.EndpointMBean.invoke(EndpointMBean.java:121) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at org.springframework.boot.actuate.endpoint.jmx.EndpointMBean.invoke(EndpointMBean.java:96) [spring-boot-actuator-2.3.2.RELEASE.jar:2.3.2.RELEASE]at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [na:1.8.0_251]at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) [na:1.8.0_251]at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) [na:1.8.0_251]at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) [na:1.8.0_251]at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) [na:1.8.0_251]at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) [na:1.8.0_251]at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) [na:1.8.0_251]at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) ~[na:na]at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_251]at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_251]at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) [na:1.8.0_251]at sun.rmi.transport.Transport$1.run(Transport.java:200) [na:1.8.0_251]at sun.rmi.transport.Transport$1.run(Transport.java:197) [na:1.8.0_251]at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_251]at sun.rmi.transport.Transport.serviceCall(Transport.java:196) [na:1.8.0_251]at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) [na:1.8.0_251]at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) [na:1.8.0_251]at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) [na:1.8.0_251]at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_251]at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) [na:1.8.0_251]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_251]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_251]at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_251]
Caused by: java.net.ConnectException: Connection refused: connectat java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) ~[na:1.8.0_251]at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) ~[na:1.8.0_251]at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_251]at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_251]at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_251]at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) ~[na:1.8.0_251]at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_251]at java.net.Socket.connect(Socket.java:606) ~[na:1.8.0_251]at com.rabbitmq.client.impl.SocketFrameHandlerFactory.create(SocketFrameHandlerFactory.java:60) ~[amqp-client-5.9.0.jar:5.9.0]at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:1137) ~[amqp-client-5.9.0.jar:5.9.0]at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:1087) ~[amqp-client-5.9.0.jar:5.9.0]at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.connectAddresses(AbstractConnectionFactory.java:560) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.connect(AbstractConnectionFactory.java:533) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.createBareConnection(AbstractConnectionFactory.java:487) ~[spring-rabbit-2.2.9.RELEASE.jar:2.2.9.RELEASE]... 50 common frames omitted

学习视频链接：尚硅谷周阳主讲SpringCloud87p

yaml配置信息

server:port: 8801   # 端口号spring:application:name: cloud-stream-provider  # 微服务名称cloud:stream:binders:   # 此处配置要绑定的rabbitmq服务信息defaultRabbit:   # 定义的名称，用于binding整合type: rabbit   # 消息组件类型environment:   # rabbitmq环境配置spring:rabbitmq:host: 192.168.232.134port: 5672username: alicepassword: 123bindings:   # 服务的整合处理output:   # 一个通道名称destination: studyExchange   # 要使用的Exchange名称content-type: application/json   # 设置消息类型，此处为json，文本设置"text/plain"binder: defaultRabbit   # 设置要绑定的消息服务的具体设置# eureka注册配置
eureka:client:#healthcheck:#enabled: true   # 开启心跳检查service-url:defaultZone: http://localhost:7001/eurekainstance:lease-renewal-interval-in-seconds: 2   # 维持心跳时间2秒(默认30秒)lease-expiration-duration-in-seconds: 5   # 超时失效时间5秒(默认90秒)instance-id: send-8801.com    # 在信息列表时显示主机名称prefer-ip-address: true    # 访问路径变为IP地址

虽然有这个错误信息，但好像不影响使用，仍然能建立连接

具体解决方案
将environment中rabbitmq的环境配置删掉，在上方重新声明配置即可

server:port: 8801   # 端口号spring:application:name: cloud-stream-provider  # 微服务名称rabbitmq:host: 192.168.232.134port: 5672username: alicepassword: 123cloud:stream:binders:   # 此处配置要绑定的rabbitmq服务信息defaultRabbit:   # 定义的名称，用于binding整合type: rabbit   # 消息组件类型
#          environment:   # rabbitmq环境配置
#            spring:
#              rabbitmq:
#                host: 192.168.232.134
#                port: 5672
#                username: alice
#                password: 123bindings:   # 服务的整合处理output:   # 一个通道名称destination: studyExchange   # 要使用的Exchange名称content-type: application/json   # 设置消息类型，此处为json，文本设置"text/plain"binder: defaultRabbit   # 设置要绑定的消息服务的具体设置# eureka注册配置
eureka:client:#healthcheck:#enabled: true   # 开启心跳检查service-url:defaultZone: http://localhost:7001/eurekainstance:lease-renewal-interval-in-seconds: 2   # 维持心跳时间2秒(默认30秒)lease-expiration-duration-in-seconds: 5   # 超时失效时间5秒(默认90秒)instance-id: send-8801.com    # 在信息列表时显示主机名称prefer-ip-address: true    # 访问路径变为IP地址

SpringCloud学习过程中遇到错误 Rabbit health check failed相关推荐

SpringCloud使用RabbitMQ报错Rabbit health check failed
问题描述:Docker容器启动RabbitMQ以后,本地环境使用Spring Cloud连接RabbitMQ,结果报错: o.s.b.a.amqp.RabbitHealthIndicator : Ra ...
Rabbit health check failed
1:首先说明这只是rabbitMq链接报错的原因之一错误原因:结合下面这张图进行说明吧,rabbitMq服务有两个端口,一个是用户服务链接的,一个是用于web页面查看信息用的,我们平时项目链接的话, ...
DataSource health check failed
警告[错误]日志 2020-06-05 10:48:56 WARN [-RMI TCP Connection(3)-192.168.0.152] [87] [org.springframework.b ...
shell学习过程中的错误集锦
1 if语句,没有加:号没有以fi结尾,报错: 在文件最后一行报错: line 53: syntax error: unexpected end of file 2 使用 if [ x$1 -ne x ...
在 Rolling Update 中使用 Health Check - 每天5分钟玩转 Docker 容器技术（146）
上一节讨论了 Health Check 在 Scale Up 中的应用,Health Check 另一个重要的应用场景是 Rolling Update.试想一下下面的情况: 现有一个正常运行的多副本应 ...
Liveness和Readiness两种Health Check手段在Kubernetes中的使用
一.概述强大的自愈能力是Kubernetes这一类容器编排管理引擎的一个重要特性.通常情况下,Kubernetes通过重启发生故障的容器来实现自愈.除此之外,我们还有其他方式来实现基于Kuberne ...
10、Health Check、及机制Liveness 探测、机制Readiness 探测、在Scale Up(伸缩)中使用Health Check、
Health Check 强大的自愈能力是 Kubernetes 这类容器编排引擎的一个重要特性.自愈的默认实现方式是自动重启发生故障的容器.除此之外,用户还可以利用 Liveness 和 Readi ...
在 Scale Up 中使用 Health Check - 每天5分钟玩转 Docker 容器技术（145）
2019独角兽企业重金招聘Python工程师标准>>> 对于多副本应用,当执行 Scale Up 操作时,新副本会作为 backend 被添加到 Service 的负责均衡中,与已有 ...
linux网络健康度检测,linux运维、架构之路-K8s健康检查Health Check
一.Health Check介绍强大的自愈能力是k8s容器编排引擎一个重要特性,自愈能力的默认实现方式为自动重启发生故障的容器,另外还可以利用Liveness和Readiness探测机制设置更精细的 ...

SpringCloud学习过程中遇到错误 Rabbit health check failed

SpringCloud学习过程中遇到错误 Rabbit health check failed相关推荐

最新文章

热门文章