背景:
在编写内部接口时,有同事在interface上用了@RequestMapping("/xxx")注解,然后在@FeignClient注解中使用了fallback,并实现了接口的fallback类,导致启动时报错:
Caused by: java.lang.IllegalStateException: Ambiguous mapping. Cannot map 'com.xxx.xxx.core.fegin.OrganizationRoleIntApi' method
com.xxx.xxx.core.fegin.OrganizationRoleIntApi#detail(String)
to {GET /organ_role_api/detail}: There is already 'organizationRoleIntFallback' bean method
com.xxx.xxx.core.fegin.rollback.OrganizationRoleIntFallback#detail(String) mapped.
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping$MappingRegistry.validateMethodMapping(AbstractHandlerMethodMapping.java:636) ~[spring-webmvc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping$MappingRegistry.register(AbstractHandlerMethodMapping.java:603) ~[spring-webmvc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.registerHandlerMethod(AbstractHandlerMethodMapping.java:318) ~[spring-webmvc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.registerHandlerMethod(RequestMappingHandlerMapping.java:377) ~[spring-webmvc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.registerHandlerMethod(RequestMappingHandlerMapping.java:74) ~[spring-webmvc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.lambda$detectHandlerMethods$1(AbstractHandlerMethodMapping.java:288) ~[spring-webmvc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping$$Lambda$955/1611272816.accept(Unknown Source) ~[na:na]
产生原因:
在服务启动时,Spring会扫描带有@RequestMapping注解的类,实现路由注册,处理@RequestMapping类为AbstractHandlerMethodMapping
具体代码:
register:
validateMethodMapping:
解决方案:
- 如果用要用@FeignClient的fallback实现熔断兜底处理,那么就不能在interface上用@RequestMapping注解,在interface中定义统一公共路由前缀即可。
- 如果要用@FeignClient的fallbackFactory实现熔断兜底处理,那么interface上的@RequestMapping注解就没有影响了,利用FallbackFactory
实现匿名内部类中各个方法的兜底处理。



