Could not extract response: no suitable HttpMessageConverter found for response type [class java.lan

最新推荐文章于 2024-07-22 17:28:32 发布
最新推荐文章于 2024-07-22 17:28:32 发布
阅读量4.8w 收藏 10
点赞数 12
分类专栏： Spring 文章标签： Spring Cloud OpenFeign HttpMessageConverter 异常处理 微服务调用 响应类型
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_37354060/article/details/124075085
版权

解决 Could not extract response: no suitable HttpMessageConverter found for response type [class java.lang.Object] and content type [text/plain;charset=UTF-8]

1. 异常情况

使用open-feign微服务间调用出现异常

2022-04-10 11:21:10.085 ERROR 19832 --- [nio-8001-exec-2] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [class java.lang.Object] and content type [text/plain;charset=UTF-8]] with root cause

org.springframework.web.client.UnknownContentTypeException: Could not extract response: no suitable HttpMessageConverter found for response type [class java.lang.Object] and content type [text/plain;charset=UTF-8]
	at org.springframework.web.client.HttpMessageConverterExtractor.extractData(HttpMessageConverterExtractor.java:126) ~[spring-web-5.3.18.jar:5.3.18]
	at org.springframework.cloud.openfeign.support.SpringDecoder.decode(SpringDecoder.java:75) ~[spring-cloud-openfeign-core-3.1.2-20220409.235253-103.jar:3.1.2-SNAPSHOT]
	at org.springframework.cloud.openfeign.support.ResponseEntityDecoder.decode(ResponseEntityDecoder.java:61) ~[spring-cloud-openfeign-core-3.1.2-20220409.235253-103.jar:3.1.2-SNAPSHOT]
	at feign.optionals.OptionalDecoder.decode(OptionalDecoder.java:36) ~[feign-core-11.8.jar:na]
	at feign.AsyncResponseHandler.decode(AsyncResponseHandler.java:115) ~[feign-core-11.8.jar:na]
	at feign.AsyncResponseHandler.handleResponse(AsyncResponseHandler.java:87) ~[feign-core-11.8.jar:na]
	at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:138) ~[feign-core-11.8.jar:na]
	at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:89) ~[feign-core-11.8.jar:na]
	at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:100) ~[feign-core-11.8.jar:na]
	at jdk.proxy2/jdk.proxy2.$Proxy125.test(Unknown Source) ~[na:na]
	at main.controller.OrderController.test(OrderController.java:40) ~[classes/:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[na:na]
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
	at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[na:na]
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) ~[spring-web-5.3.18.jar:5.3.18]
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:150) ~[spring-web-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:117) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:895) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:808) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1067) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:963) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:655) ~[tomcat-embed-core-9.0.60.jar:4.0.FR]
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) ~[spring-webmvc-5.3.18.jar:5.3.18]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) ~[tomcat-embed-core-9.0.60.jar:4.0.FR]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat-embed-websocket-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) ~[spring-web-5.3.18.jar:5.3.18]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.18.jar:5.3.18]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) ~[spring-web-5.3.18.jar:5.3.18]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.18.jar:5.3.18]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[spring-web-5.3.18.jar:5.3.18]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.18.jar:5.3.18]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-embed-core-9.0.60.jar:9.0.60]
	at java.base/java.lang.Thread.run(Thread.java:833) ~[na:na]

2. 现场状态

发送方Controller

@RestController
@RequestMapping("/order")
@RequiredArgsConstructor
public class OrderController {

    private final Client client;

    @GetMapping("/test")
    public Object test() {
        System.out.println(client.test());
        return "1124";
    }

}

Client

@FeignClient(name = "stock")
public interface Client {

    @PostMapping("/stock/test")
    Object test();
}

接收方Controller

@RestController
@RequestMapping("/stock")
public class StockController {

    @PostMapping("/test")
    public Object test() {
        return "123";
    }
}

3. 解决方法

改变Client中的请求方法的返回值, 改为String
在这里插入图片描述

@FeignClient(name = "stock")
public interface Client {

    @PostMapping("/stock/test")
    String test();
}
_ZestyJt
关注
专栏目录
SpringBoot单元测试java.lang.IllegalStateException Could not initialize plugin: interface org.mockito解决方案
weixin_43178406的博客
12-16 3万+
本文主要介绍了SpringBoot项目单元测试java.lang.IllegalStateException: Could not initialize plugin: interface org.mockito.plugins.MockMaker，希望能对使用SpringBoot项目单元测试的同学们有所帮助。 文章目录 1. 问题描述 2. 原因分析 3. 解决办法
【源码分析】OpenFeign 报错：Could not extract response no suitable HttpMessageConverter found for response
最新发布
甘蓝的专栏
08-13 273
OpenFeign找不到合适的HttpMessageConverter？源码分析，找到根本原因并解决
feign.FeignException$MethodNotAllowed: status 405 reading xxx#yyy(Integer)
时间静止
09-05 1万+
异常信息 : 使用feign 调用异常 feign.FeignException$MethodNotAllowed: status 405 reading ConsumerService#findById(Integer) 详细信息: feign.FeignException$MethodNotAllowed: status 405 reading ConsumerService#findById...
解决:Could not extract response: no suitable HttpMessageConverter found for content type [xxx]
菜鸡的博客
04-27 8058
解决:Could not extract response: no suitable HttpMessageConverter found for content type [xxx]
Could not extract response: no suitable HttpMessageConverter
阿呆的专栏
02-26 1万+
版本：spring-cloud-openfeign-core-2.1.1.RELEASE.jar，spring-webmvc-5.1.14.RELEASE.jar，jetty-server-9.4.41.v20210516.jar，tomcat-embed-core-9.0.48.jar。
Could not extract response: no suitable HttpMessageConverter found for content type [text/html]
小草莓的博客
02-13 1万+
}
Fegin 错误 Could not extract response: no suitable HttpMessageConverter found for XXX
大鹏小站的博客
11-27 6835
问题： 这两天用Fegin 调用其他小组的下载接口报错 feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [class com.XXX…manager.dto.HaloResponse] and content type [application/octet-stream;charset=UTF-8] 原因： 对方返回的结果用pos
使用springcloud Fegin上传文件报错Could not write request: no suitable HttpMessageConverter found for request
smartdt的博客
05-11 1万+
一、问题简介 在springcloud微服务中，需要用到feign去调用文件上传的服务，如通过fastdfs文件服务器上传文件： 1、fegin的接口配置（服务降级代码：略～） @FeignClient(value = "XXXXXXXX-XXXXX-PROVIDER", fallbackFactory = XxxxxxClientFallbackFactory.class) pub...
Feign调用错误no suitable HttpMessageConverter found for response type
BorisCao的博客
06-08 1883
feign调用时，数据转换失败
【Spring】No suitable HttpMessageConverter repsonse type
九师兄
04-08 383
1.概述 一个flink项目，然后我修改了一下报错了，错误如下 Caused by: feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [com. BaasResponse<java.util.List.DictRead>>] and content type [application/ json] at fei
Could not extract response: no suitable HttpMessageConverter found for response type
u012609879的博客
08-20 5790
Could not extract response: no suitable HttpMessageConverter found for response type [class com.XXX] and content type [text/plain] 1. 报错 feign.codec.DecodeException: Could not extract response: no sui...
Could not extract response: no suitable HttpMessageConverter found for ..content type [text/html...]
weixin_43860634的博客
09-04 5211
Could not extract response: no suitable HttpMessageConverter found for ..content type [text/html...]
RestTemplate请求：Could not extract response: no suitable HttpMessageConverter found for response type
热门推荐
TanaStudy的博客
09-23 2万+
1、问题描述 使用RestTemplate发请求时出现Could not extract response: no suitable HttpMessageConverter found for response type.... content type [text/html;charset=UTF-8]的问题，具体错误如下： org.springframework.web.client.UnknownContentTypeException: Could not extract response: no
RestTemplate请求Could not extract response: no suitable HttpMessageConverter found for response type..
z69183787的专栏
05-07 5877
使用 Spring Boot 写项目，需要用到微信接口获取用户信息。 在 Jessey 和 Spring RestTemplate 两个 Rest 客户端中，想到尽量不引入更多的东西，然后就选择了 Spring RestTemplate 作为 网络请求的 Client，然后就被微信接口摆了一道，然后踩了一个 RestTemplate 的坑。 二、第一个坑：被微信摆了一道 报错信息是： org.springframework.web.client.RestClientException: Could n
feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for
m0_52767002的博客
07-22 1705
Could not extract response: no suitable HttpMessageConverter found for response type [xxx] and content type [application/octet-stream] feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [xxx]
Could not extract response: no suitable HttpMessageConverter found for response type [class xx] and
你当像鸟飞往你的山~~
05-16 1万+
springboot使用RestTemplate报错：Could not extract response: no suitable HttpMessageConverter found for response type [class xx] and … spring boot版本大于1.4的时候，spring boot不会再自动装配定义一个RestTemplate，需要手动创建，用一下代...
记录：Could not extract response: no suitable HttpMessageConverter found for respo
CMEguagua的博客
12-01 2886
使用 RestTemplate 请求接口设置JSONObject 为返回对象，content-type:text/plain;charset-utf-8 接口正常返回结构了，转换响应体时报找不到合适的 HttpMessageConverter 看了下RestTemplate 的配置只设置了 MediaType.TEXT_PLAIN MediaType.TEXT_HTML 新加了json的返回就正常了 MediaType.APPLICATION_JSON MediaType.APPLICATION_O.
Could not extract response: no suitable HttpMessageConverter found for content type [xxx]
11-17
当我们使用Spring RestTemplate进行HTTP请求时，有时会遇到"Could not extract response: no suitable HttpMessageConverter found for content type [xxx]"的错误。这是因为RestTemplate默认使用的HttpMessageConverter无法处理返回的数据类型。解决这个问题的方法是添加一个能够处理该数据类型的HttpMessageConverter。 以下是两种解决方法： 1.使用MappingJackson2HttpMessageConverter ```java RestTemplate restTemplate = new RestTemplate(); MappingJackson2HttpMessageConverter converter = new MappingJackson2HttpMessageConverter(); converter.setSupportedMediaTypes(Collections.singletonList(MediaType.valueOf("application/vnd.github.v3+json"))); restTemplate.getMessageConverters().add(converter); ``` 2.自定义HttpMessageConverter ```java public class MyHttpMessageConverter extends AbstractHttpMessageConverter<Object> { public MyHttpMessageConverter() { super(MediaType.valueOf("application/vnd.github.v3+json")); } @Override protected boolean supports(Class<?> clazz) { return true; } @Override protected Object readInternal(Class<?> clazz, HttpInputMessage inputMessage) throws IOException, HttpMessageNotReadableException { // 处理返回的数据 return null; } @Override protected void writeInternal(Object o, HttpOutputMessage outputMessage) throws IOException, HttpMessageNotWritableException { // 处理发送的数据 } } ``` 然后将自定义的HttpMessageConverter添加到RestTemplate中： ```java RestTemplate restTemplate = new RestTemplate(); restTemplate.getMessageConverters().add(new MyHttpMessageConverter()); ```
评论 9
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值