Description: The bean ‘**.FeignClientSpecification’, defined in null, could not be registered. A bea

团y子

已于 2022-11-14 13:25:18 修改

阅读量1.6k

点赞数 1

分类专栏：配置文章标签： vue.js

于 2021-06-08 09:45:21 首次发布

本文链接：https://blog.csdn.net/weixin_47744694/article/details/117689630

版权

配置专栏收录该内容

2 篇文章 0 订阅

订阅专栏

Description:

The bean ‘**.FeignClientSpecification’, defined in null, could not be registered. A bean with that name has already been defined in null and overriding is disabled.

1.这是Feign调用报错

2.这是在开发springcloud的时候,把多个消费者放在一个控制层的包的里的时候会报这个错,那是因为，多个同名的消费者早在注册中心都是同名注册的

在这里插入图片描述

3.要添加的配置

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

团y子

关注关注

1
点赞
踩
2

收藏

觉得还不错? 一键收藏
0
评论
复制链接

分享到 QQ

分享到新浪微博

扫一扫

专栏目录

The bean ‘xxx-xxx.FeignClientSpecification‘, defined in null, could not be registered. A bean with t

hkl_Forever的博客

08-24

753

此错误是因为spring容器中存在相同名称的bean对象，在yml配置文件中配置代码。

详细解决redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool

念兮为美

03-18

1万+

redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool的多种详细的解决方法

参与评论您还未登录，请先登录后发表或查看评论

OpenFeign 出现The bean xxx.FeignClientSpecification could not be registered问题解决

最新发布

morris

08-23

448

在一个项目中，如果有多个FeignClient客户端指向同一个微服务，项目启动的过程中可能会抛出如下的异常。

The bean ‘FeignClientSpecification‘ could not be registered. A bean with that name has

weixin_70044963的博客

06-24

1114

使用FeignClient注解中的contextId来区分2个相同的bean。服务器使用feign调用其他服务时，创建的apiBean命名冲突导致异常。或者直接将两个bean合并为1个bean。

feign报the bean 'item-service.FeignClientSpecification', defined in null, could not be registered.错误

qq_41571395的博客

02-22

2098

刚开始学习使用feign，遇到报错 Description: The bean 'item-service.FeignClientSpecification', defined in null, could not be registered. A bean with that name has already been defined in null and overriding is di...

解决The bean ‘XXX.FeignClientSpecification‘ could not be registered

qq_41591215的博客

04-01

2468

解决完，紧接着就出现这个问题The bean ‘XXX.FeignClientSpecification’ could not be registered.A bean with that name has already been defined and overriding is disabled.

FeignClientSpecification could not be registered

liu346487291的专栏

08-05

2771

spring cloud feign FeignClientSpecification @FeignClient

升级SpringCloud到Hoxton.SR3出现The bean ‘xxx.FeignClientSpecification’ could not be registered. 源码分析和解决

12-21

在升级Spring Cloud从Finchley.SR2到Hoxton.SR3的过程中，开发者可能会遇到一个启动时的错误，提示"The bean ‘xxx.FeignClientSpecification’ could not be registered. A bean with that name has already been ...

springcloud集成feign进行远程调用时出现@FeignClient同名问题:The bean 'content.FeignClientSpecification', defined in

Slovef的博客

08-23

2190

springcloud集成feign进行远程调用时出现@FeignClient同名问题 1.问题描述: 2019-08-15 15:01:35.652 ERROR 11744 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPLICATION FA...

The bean ‘xxxx.FeignClientSpecification‘ could not be registered. A bean with that name has already

程金鹏（程利鹏）

09-06

3958

The bean 'xxxx.FeignClientSpecification' could not be registered. A bean with that name has already been defined and overriding is disabled.

The bean ‘FeignClientSpecification‘ could not be registered. A bean with that name has already

fusugongzi的博客

04-24

4408

项目或项目依赖，存在同名的feign client。

Feign报错“The bean 'xxx.FeignClientSpecification', defined in null,could not be registered”

qq_38340677的博客

04-11

5362

SpringCloud整合Feign报错： Description: The bean 'spring-feign-provider.FeignClientSpecification', defined in null, could not be registered. A bean with that name has already been defined in null and ove...

The bean FeignClientSpecification could not be registered. A bean with that name has already been

进击的小白

11-23

8668

现象客户端使用feign调用服务api时,启动出现异常如下: ERROR 41681 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPLICATION FAILED TO START *************************** Description: The bean 'LIZZ-PROVIDER.FeignClientSpecific

Feign调用报错The bean ‘XXX.FeignClientSpecification‘, defined in null, could not be registered....的解决办法升

weixin_43920778的博客

01-20

8369

升级Spring Boot 2.1.0 Spring Cloud Greenwich.M1 版本后，在2个Feign接口类内定义相同的名字， @FeignClient(name = 相同的名字就会出现报错，在之前的版本不会提示报错，报错内容为The bean ‘XXX.FeignClientSpecification’, defined in null, could not be registered. A bean with that name has already been defined in

FeignClientSpecification‘ could not be registered. A bean with that name has already been defined

王广帅--游戏开发技术

12-04

7817

在使用OpenFeign调用时，如果目标服务只有一个，而我们想将调用接口分成两个service类，有时间会报这个错： FeignClientSpecification’ could not be registered. A bean with that name has already been defined and overriding is disabled

解决The bean ‘xxxx.FeignClientSpecification‘ could not be registered. 问题

m0_64894277的博客

11-29

3123

3.在@FeignClient增加contextId,contextId不能重复。1.把feign的代码进行合并（不建议：代码太杂乱）

Feign远程调用报错（The bean ‘course-service.FeignClientSpecification‘ could not be registered）已解决

日常学习总结

10-18

1244

Feign远程调用服务无法启动，The bean 'course-service.FeignClientSpecification' could not be registered. A bean with that name has already been defined and overriding is disabled.

The bean ‘xxx.FeignClientSpecification‘ could not be registered. A bean with that name has already b

weixin_70144763的博客

04-27

9969

比如：项目中定义了两个feign接口类，但是注解都是@FeignClient(value = "userinfo-service")为此报错了。将调用同一个服务的fegin接口都写到一个LogReqFeign接口类中。但是我这里不合适，我远程调用的方法都是同名的。在同于一个微服务中多个feign接口使用@FeignClient注解调用同一个名称的微服务，启动时引发的异常。来允许bean覆盖，但是这种方式并不推荐，因为可能会导致意外的覆盖，导致应用程序出现其他问题。

The bean 'Call.FeignClientSpecification' could not be registered. A bean with that name has already been defined and overriding is disabled.

09-06

This error indicates that there is a conflict in the Spring bean configuration. The bean named 'Call.FeignClientSpecification' is being registered multiple times, which is not allowed by default. Spring considers this as an error and throws an exception. To resolve this issue, there are a few possible solutions: 1. Check your codebase for duplicate bean definitions. Make sure you are not accidentally registering the same bean multiple times. 2. If you intentionally have multiple bean definitions for 'Call.FeignClientSpecification', you can enable bean overriding by adding the following property to your application.properties or application.yml file: ``` spring.main.allow-bean-definition-overriding=true ``` However, be cautious when using this approach, as it may lead to unexpected behavior if there are conflicting bean definitions. 3. If you are using Spring Boot, you can use the '@Primary' annotation on one of the bean definitions to specify which one should take precedence in case of conflicts. For example: ```java @Primary @Bean public Call.FeignClientSpecification primaryFeignClientSpecification() { // bean definition } ``` This will mark the bean as primary and resolve any conflicts. I hope this helps! Let me know if you have any further questions.