springcloud:访问/bus/refresh地址后出现错误，，client端出现以下错误

springcloud config-server rabbitmq
配置自动刷新,在访问/bus/refresh地址后，client端出现以下错误

client-config

org.springframework.amqp.rabbit.listener.exception.ListenerExecutionFailedException: Listener threw exception

at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.wrapToListenerExecutionFailedExceptionIfNeeded(AbstractMessageListenerContainer.java:1506) ~[spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:1417) ~[spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.actualInvokeListener(AbstractMessageListenerContainer.java:1337) ~[spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:1324) ~[spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.executeListener(AbstractMessageListenerContainer.java:1303) ~[spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.doReceiveAndExecute(SimpleMessageListenerContainer.java:785) [spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.receiveAndExecute(SimpleMessageListenerContainer.java:769) [spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$700(SimpleMessageListenerContainer.java:77) [spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.run(SimpleMessageListenerContainer.java:1010) [spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]

Caused by: org.springframework.messaging.converter.MessageConversionException:
Cannot convert from [java.lang.String] to
[org.springframework.cloud.bus.event.RemoteApplicationEvent]
for GenericMessage [payload={"type":"RefreshRemoteApplicationEvent","timestamp":1522749739659,"originService":"config-server:8888","destinationService":"**","id":"202be12a-7597-45a9-8731-bb4454e4da4f"},
headers={amqp_receivedDeliveryMode=PERSISTENT,
amqp_receivedExchange=springCloudBus, amqp_deliveryTag=1,
deliveryAttempt=3,
amqp_consumerQueue=springCloudBus.anonymous.9cLCAd4QRVCfurGMHUDmrg,
X-B3-ParentSpanId=c5f8bad949d06b94,
amqp_redelivered=false, messageSent=true,
spanTraceId=5daa65f9b6124b03, spanId=3e738e68342e56ad, spanParentSpanId=c5f8bad949d06b94,
amqp_receivedRoutingKey=springCloudBus, nativeHeaders={spanTraceId=[5daa65f9b6124b03], spanId=[3e738e68342e56ad], spanParentSpanId=[c5f8bad949d06b94], spanSampled=[0]}, X-B3-SpanId=3e738e68342e56ad, X-B3-Sampled=0, X-B3-TraceId=5daa65f9b6124b03, id=d01f292e-7a7f-dec5-c49b-50fc36e6b1b3, spanSampled=0, amqp_consumerTag=amq.ctag-HJJsrtYoTr5gc-g7fUQFkA, contentType=text/plain}]

at org.springframework.messaging.handler.annotation.support.PayloadArgumentResolver.resolveArgument(PayloadArgumentResolver.java:144) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.messaging.handler.invocation.HandlerMethodArgumentResolverComposite.resolveArgument(HandlerMethodArgumentResolverComposite.java:116) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.getMethodArgumentValues(InvocableHandlerMethod.java:137) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:109) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.cloud.stream.binding.StreamListenerMessageHandler.handleRequestMessage(StreamListenerMessageHandler.java:55) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:109) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:164) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:116) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:132) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:105) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:73) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:463) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:407) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:181) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:160) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:47) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:108) ~[spring-messaging-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at org.springframework.integration.endpoint.MessageProducerSupport.sendMessage(MessageProducerSupport.java:203) ~[spring-integration-core-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.amqp.inbound.AmqpInboundChannelAdapter.access$1100(AmqpInboundChannelAdapter.java:59) ~[spring-integration-amqp-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.integration.amqp.inbound.AmqpInboundChannelAdapter$Listener.lambda$onMessage$0(AmqpInboundChannelAdapter.java:217) ~[spring-integration-amqp-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.retry.support.RetryTemplate.doExecute(RetryTemplate.java:287) ~[spring-retry-1.2.2.RELEASE.jar:na]
at org.springframework.retry.support.RetryTemplate.execute(RetryTemplate.java:180) ~[spring-retry-1.2.2.RELEASE.jar:na]
at org.springframework.integration.amqp.inbound.AmqpInboundChannelAdapter$Listener.onMessage(AmqpInboundChannelAdapter.java:214) ~[spring-integration-amqp-5.0.3.RELEASE.jar:5.0.3.RELEASE]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:1414) ~[spring-rabbit-2.0.2.RELEASE.jar:2.0.2.RELEASE]
... 8 common frames omitted

2018-04-03 18:02:22.789 WARN [user-service,,,] 9428 --- [VCfurGMHUDmrg-1] ingErrorHandler$DefaultExceptionStrategy : Fatal message conversion error; message rejected; it will be dropped or routed to a dead letter exchange, if so configured: (Body:'{"type":"RefreshRemoteApplicationEvent","timestamp":1522749739659,"originService":"config-server:8888","destinationService":"**","id":"202be12a-7597-45a9-8731-bb4454e4da4f"}' MessageProperties [headers={spanTraceId=5daa65f9b6124b03, spanId=8e507c0a47a5fd86, nativeHeaders={spanTraceId=[5daa65f9b6124b03], spanId=[3e738e68342e56ad], spanParentSpanId=[c5f8bad949d06b94], spanSampled=[0]}, messageSent=true, spanSampled=0, contentType=text/plain, originalContentType=application/json;charset=UTF-8}, contentType=text/plain, contentLength=0, receivedDeliveryMode=PERSISTENT, priority=0, redelivered=false, receivedExchange=springCloudBus, receivedRoutingKey=springCloudBus, deliveryTag=1, consumerTag=amq.ctag-HJJsrtYoTr5gc-g7fUQFkA, consumerQueue=springCloudBus.anonymous.9cLCAd4QRVCfurGMHUDmrg])
2018-04-03 18:02:25.803 WARN [user-service,,,] 9428 --- [VCfurGMHUDmrg-1] s.a.r.l.ConditionalRejectingErrorHandler : Execution of Rabbit message listener failed.

图片说明

==================================已解决===================================
==================================已解决===================================
==================================已解决===================================
==================================已解决===================================
Spring boot 2.0的改动较大，/bus/refresh全部整合到actuador里面了，所以之前1.x的management.security.enabled全部失效，不适用于2.0
适用于2.0的配置是这样的：

 management:
  endpoints:
    web:
      exposure:
        include: bus-refresh

另外注解

 @RefreshScope

需要在配置的页面加上，就是说附带@Value的页面加上此注解

请求刷新的页面由原来1.5.x的localhost:8888/bus/refresh
变成：http://localhost:8888/actuator/bus-refresh

注意：config-server和config-client的配置都得加上

 management:
  endpoints:
    web:
      exposure:
        include: bus-refresh

配置
整合被折腾了好几天，实在是大坑

写回答
好问题 0 提建议
追加酬金
关注问题
分享
邀请回答
编辑收藏删除结题
收藏举报

6条回答

关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
新时代的程序猿 2018-04-03 10:25
关注
异常信息不完整，截个全的来看看

本回答被题主选为最佳回答 , 对您是否有帮助呢?

解决无用
评论打赏
分享
举报

评论

按下Enter换行，Ctrl+Enter发表内容

查看更多回答(5条)

报告相同问题？

关注问题

springcloud:访问/bus/refresh地址后出现错误，，client端出现以下错误
2018-04-03 10:14

回答 6 已采纳异常信息不完整，截个全的来看看
spring cloud /bus/refresh接口返回405 spring
2018-03-15 02:59

回答 3 已采纳启动日志里面没有映射到/bus/refresh 我真是日乐uzi了什么包也没缺啊配置文件应该也没错啊
学习springcloud时，学习到openfeign的时候启动feign-order80时报错：'http://localhost:8761/eureka，如何解决？ spring cloud
2022-03-02 21:03

回答 1 已采纳 #报错：Request execution error. endpoint=DefaultEndpoint{ serviceUrl='http://localhost:8761/eureka/}错误原
springcloud:访问/bus/refresh地址后出现错误，，client端出现以下错误
2018-10-18 14:21

weixin_30542079的博客 springcloud config-server rabbitmq配置自动刷新,在访问/bus/refresh地址后，client端出现以下错误 client-config org.springframework.amqp.rabbit.listener.exception.ListenerExecutionFailedException: ...
nacos + gateway 在配置 lb://服务名，时无效报503，求各位大佬帮帮忙。。。 java
2021-06-02 23:11

回答 3 已采纳已经找到问题所在了，问题不是出现在代码上，是出现在nacos的配置上。原来是给每一个服务配置了一个命名空间，然后对应服务的配置，放在对应的命名空间中，这样看着很简洁干净，这样其实也是没问题的。
spring cloud Oauth2.0 使用refresh token 获取到的新的refresh token 无法进行刷新Token java spring
2020-10-10 16:51

回答 2 已采纳 https://blog.csdn.net/liuminglei1987/article/details/103763106/
nacos配置springcloud时出现问题 spring cloud 微服务
2022-11-15 12:14

回答 2 已采纳 nacos配置文件有错 [完美解决] Failed to start bean ‘webServerStartStop‘； nested exception is ja
Springcloud bus总线访问http://localhost:3344/actuator/bus-refresh刷新配置提示405
2021-05-08 22:30

stepBackFK的博客这个是spring下面的配置 # 切记这个一定要开，要不然报405 bus: refresh: enabled: true yml全套： server: port: 3344 eureka: client: service-url: defaultZone: ...
配置Nacos + Nginx + Spring Cloud出的问题 java nginx spring cloud
2021-10-29 19:23

回答 1 已采纳 1.如果访问ip要于linux系统的一致,需要在本地修改hosts文件绑定.2.你的nacos以集群模式启动,你看看你的配置文件中有没有配置集群模式,Nginx有没有负载均衡
java.lang.NoClassDefFoundError: org/springframework/dao/DataAccessException hibernate spring
2012-07-26 14:31

回答 3 已采纳缺少：org.springframework.transaction-3.0.5.RELEASE.jar
SpringCloud2021.0.1 + SpringCloud 阿里巴巴 2021.0.1.0配置Seata后出现找不到事务分组 java spring cloud 后端
2022-05-30 14:49

回答 1 已采纳 seataServer.properties 贴出来看看或者SL我
SpringCloud2021 访问/actuator/bus-refresh，提示405，“Request method ‘POST‘ not supported“
2023-09-06 19:48

one direction--的博客 1.首先需注意，springcloud2021新版中bus-refresh接口改为busrefresh；5.至此，client端配置可以正常刷新；
在linux宝塔面板上运行的spring boot出现日志报出以下错误 java linux spring boot
2022-09-06 22:40

回答 1 已采纳 Caused by: java.lang.IllegalStateException: Failed to create access log directory '../log/access' 异常
SpringCloud消息总线RabbitMQ+Bus-Refresh接口触发所有config-client自动重新读取配置文件
2018-04-27 18:37

实践方志鹏博客搭建Springcloud+RabbitMQ+Config-client+config-server Eureka-server的微服务架构，通过/bus/refresh接口触发所有config-client自动从config-server重新读取配置文件。SpringCloud和SpringBoot版本...
Spring Cloud Bus 无法 bus-refresh 问题
2022-04-22 16:08

web13985085406的博客环境： Spring Cloud : Greenwich.RELEASE Spring Cloud Config:2.1.0.RELEASE ...Spring Cloud Config 通过 Spring Cloud Bus 配置更新. 通过 http://localhost:8888/actuator/bus-refresh 进行刷新提
springcloud搭建消息总线出现的问题记录------/bus/refresh报404错误
2020-08-18 15:03

捉猫鼠的博客为springcloud搭建消息总线完毕访问/bus/refresh报404错误经过查询发现/bus/refresh是springboot1.xx的写法。 Spring boot 2.0的改动较大，/bus/refresh全部整合到actuador里面了，所以之前1.x的management....
SpringCloud Bus 动态刷新遇见的500错误
2020-08-25 18:15

风趣又端庄的博客今天看到周阳老师的视频，是SpringCloud Bus 动态刷新全局广播和定点通知。链接为https://www.bilibili.com/video/BV18E411x7eT?p=81。在命令行发送 curl -X POST "http://localhost:3344/actuator/bus-refresh" ...
在写springcloud项目中，关于手动刷新http://localhost:8771/actuator/busrefresh报错404
2022-08-16 10:52

学爪哇的博客 springcloud微服务，消息总线结合config配置中心，手动刷新报错
没有解决我的问题, 去提问

悬赏问题

¥15 js调用html页面需要隐藏某个按钮
¥15 ads仿真结果在圆图上是怎么读数的
¥20 Cotex M3的调试和程序执行方式是什么样的？
¥20 java项目连接sqlserver时报ssl相关错误
¥15 一道python难题3
¥15 牛顿斯科特系数表表示
¥15 arduino 步进电机
¥20 程序进入HardFault_Handler
¥15 oracle集群安装出bug
¥15 关于#python#的问题：自动化测试