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

最新推荐文章于 2022-12-14 18:02:26 发布
最新推荐文章于 2022-12-14 18:02:26 发布
阅读量560 收藏
点赞数
文章标签： java 大数据 json
原文链接：http://www.cnblogs.com/powerwu/articles/9810234.html
版权

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

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

转载于:https://www.cnblogs.com/powerwu/articles/9810234.html

weixin_30542079
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
SpringCloud消息总线RabbitMQ+Bus-Refresh接口触发所有config-client自动重新读取配置文件
04-27
实践方志鹏博客搭建Springcloud+RabbitMQ+Config-client+config-server Eureka-server的微服务架构，通过/bus/refresh接口触发所有config-client自动从config-server重新读取配置文件。SpringCloud和SpringBoot版本...
cloudconfig:spring-cloud-config配置中心通过消息总线实现实时刷新demo
05-13
1. 添加Spring Cloud Bus依赖：在Config Server和Client应用的pom.xml中，引入`spring-cloud-starter-bus-amqp`或`spring-cloud-starter-bus-kafka`，根据所选的消息总线选择对应的依赖。 2. 配置消息总线：在...
Spring Cloud Bus 无法 bus-refresh 问题
fortunecat0814的博客
03-26 3286
环境： Spring Cloud : Greenwich.RELEASE Spring Cloud Config:2.1.0.RELEASE Spring Cloud Bus:2.1.0.RELEASE Spring Boot: 2.1.3.RELEASE Spring boot Admin:2.1.3 问题描述： ...
Spring Cloud使用Bus的refresh刷新配置文件报异常错误
狗头神教
10-25 4855
Spring Cloud使用Bus的refresh刷新配置文件报异常: Caused by: java.lang.IllegalStateException: The configuration of the pool is sealed once started. Use HikariConfigMXBean for runtime changes. at com.zaxxer.hikari....
线程池4种拒绝策略
maqinchaoTnT的博客
08-17 301
package com.mqc.some; import java.util.concurrent.*; public class ThreadPoolTest { public static void main(String[] args) { ExecutorService executorService= new ThreadPoolExecutor(1, 1, 0L, TimeUnit.M...
spring-cloud出现线程池异常
qq_32272499的博客
01-25 3318
2018-01-25 14:34:51.488 [AsyncResolver-bootstrap-0] WARN  com.netflix.discovery.TimedSupervisorTask - task supervisor shutting down, reject the task java.util.concurrent.RejectedExecutionException:
SpringCloud bus-refresh 404
u014580040的博客
09-18 481
今天遇到个问题纠结了很久时间，网上说的 management: endpoints: web: exposure: include："*" 这也许能解决大部分人员的问题的确，但我确不是这个问题，如果你用的版本跟我一样： Spring Boot: 2.1.3.RELEASE Spring boot Admin:2.1.3 那么你可能遇到和我一样的版...
springcloud-config：springcloud
02-09
SpringCloud Config 提供了 /refresh 端点，允许在运行时刷新配置，这样配置的变更会立即生效。这在进行滚动更新或蓝绿部署时非常有用。 **6. 监听配置变化** 通过监听 Config Server 的变化，Config Client 可以...
详解使用spring cloud config来统一管理配置文件
08-26
在 `pom.xml` 文件中，引入 `spring-cloud-config-server` 和 `spring-cloud-starter-eureka-server`（如果使用 Eureka 进行服务注册和发现），以及 `spring-cloud-starter-bus-amqp`（用于通过 AMQP 协议广播配置...
springcloud配置中心个人demo
04-30
SpringCloud Config 是一个分布式系统配置管理工具，它允许在分布式系统的不同组件之间集中管理和动态更新配置。本项目是一个个人实现的 SpringCloud Config 的演示示例，旨在帮助理解其工作原理和使用方法。以下是...
springcloudBus 2.x 事件追踪
weixin_30314631的博客
06-16 164
最近由于工作需要，需要根据springcloudconfigserver搭建自己的配置管理服务，关于怎么搭建，怎么刷新等通过搜索网上资料很快完成，但是为了使我们的配置服务更完美，开始研究如果有多个conifig client实例的时候，其中一个实例进行配置刷新的时候，怎么保证或者追踪其他实例是否成功刷新，一开始网上搜索大致都说通过调用刷新端点（actuator/bus-refresh）后，调用...
请求服务无响应Dispatcher has no subscribers
qq_34254090的博客
09-09 1638
Dispatcher has no subscribers
Spring Cloud入门教程(十)：消息总线(Bus)
HYhhhhhhh的博客
06-30 648
Spring Cloud入门教程系列： Spring Cloud入门教程(一)：服务治理(Eureka) Spring Cloud入门教程(二)：客户端负载均衡(Ribbon) Spring Cloud入门教程(三)：声明式服务调用(Feign) Spring Cloud入门教程(四)：微服务容错保护(Hystrix) Spring Cloud入门教程(五)：API服务网关(Zuul) 上 Spring Cloud入门教程(六)：API服务网关(Zuul) 下 Spring Cloud入门教程(七)：分布
Listener method could not be invoked with the incoming message和 Cannot convert from [java.lang.Strin
热门推荐
天道酬勤
07-03 1万+
记录一下入门RabbitMQ问题 问题： org.springframework.amqp.rabbit.listener.exception.ListenerExecutionFailedException: Listener method could not be invoked with the incoming message 和 org.springframework.messaging...
Spring Cloud Stream：消费失败后的处理策略（一）：自动重试
weixin_42073629的博客
07-19 1118
首先，介绍一下Spring Cloud Stream中默认就已经配置了的一个异常解决方案：重试！ 应用场景 依然要明确一点，任何解决方案都要结合具体的业务实现来确定，不要有了锤子看什么问题都是钉子。那么重试可以解决什么问题呢？由于重试的基础逻辑并不会改变，所以通常重试只能解决因环境不稳定等外在因素导致的失败情况，比如：当我们接收到某个消息之后，需要调用一个外部的Web Service做一些事情，这个时候如果与外部系统的网络出现了抖动，导致调用失败而抛出异常。这个时候，通过重试消息消费的具体逻辑，可能在下
springcloud服务间调用连接超时 read Timeout
知世俗而不世俗
11-04 1万+
起因 在使用SpringCloud进行服务间调用时出现连接超时的错误，错误信息：Read timed out executing GET http://service-batch/batchmanagement/datatransfer/querybyplanid?planid=PL00000102。 原因 用idea开发debug模式调试代码时，在处理服务间调用时，由于debug模式调试代码花费...
rocketmq相关错误
qq_35008624的博客
12-14 2167
线上rocketmq消息异常
spring cloud gateway 报错 cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory
霓虹深处
08-14 9458
今天用从zuul网关换到spring cloud gateway网关，配置好项目后访问报错如下： java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDa...
Spring Cloud Bus
BLOG域名:programb.blog.csdn.net
03-04 657
Spring Cloud Bus links nodes of a distributed system with a lightweight message broker. This can then be used to broadcast state changes (e.g. configuration changes) or other management instructions. ...
http://localhost:7900/actuator/bus-refresh
最新发布
09-13
然而，根据我的理解，这个地址并没有直接与Spring Cloud Bus和Kafka相关联。实际上，正确的地址应该是"http://localhost:8881/bus/refresh"。这个请求地址是用于通过Spring Cloud Bus和Kafka来实现配置自动刷新的。 ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值