[micro service sentinel] sentinel integrates openfeign

step

We talked about sentinel Annotations @SentinelResource And its handling of abnormal disclosure scheme .

If each interface is handled separately , There will be many inconveniences , So we can integrate openfeign Unified treatment of current limiting and degradation strategies .

First step ： open feign Yes sentinel Support for

feign:
  sentinel:
    enabled: true

The second step ： Prepare the bottom plan

import com.ossa.feign.api.producer.ProducerFeign;
import org.springframework.stereotype.Service;

/** * @author issavior */
@Service
public class ProducerFeignFallback implements ProducerFeign {
    
    @Override
    public String producerById(String id) {
    
        String msg = "fallback Current limiting method ";
        return id + msg;
    }
}

The third step ： modify @FeignClient annotation

import com.ossa.feign.config.FeignClientConfig;
import com.ossa.feign.fallback.ProducerFeignFallback;
import org.springframework.cloud.openfeign.FeignClient;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.PathVariable;

/** * @author issavior */
@FeignClient(value = "ossa-service-producer", configuration = FeignClientConfig.class,fallback = ProducerFeignFallback.class)
public interface ProducerFeign {
    

    /** *  according to ID Query products  * * @param id  The primary key of the item ID * @return  Information about related products  */
    @GetMapping(value = "/producer/{id}")
    String producerById(@PathVariable("id") String id);

}

problem

Problem description ：

Caused by: java.lang.IllegalStateException: Ambiguous mapping

analysis ：

stay feign On the interface @RequestMapping annotation , It will lead to this problem .

Controller This control layer request maps two methods , And in Controller It's repeated. , So wrong reporting . Or say , If there are two in a project @RequestMapping(“/xxx”） Exactly the same will report java.lang.IllegalStateException,controller The module depends on client It is the module that causes the conflict .

Solution ：

Get rid of @RequestMapping