feign | Feign makes writing java http clients | HTTP library

try @EnableFeignClients in your main class:

I would propose to take a look in the RateLimiter direction. Maybe it does not work as expected, depending on the number of requests your application does over time. From the Javadoc for Ratelimiter: "It is important to note that the number of permits requested never affects the throttling of the request itself ... but it affects the throttling of the next request. I.e., if an expensive task arrives at an idle RateLimiter, it will be granted immediately, but it is the next request that will experience extra throttling, thus paying for the cost of the expensive task." Also helpful might be this discussion: github or github

I could imaginge there is some throttling adding up or other effect in the RateLimiter, i would try to play around with it and make sure this thing really works the way you want. Alternatively, consider using Spring @Scheduled to read from your queue. You might want to spice it up using embedded JMS for further goodies (message persistence etc).

Since you are marking FeignClientConfiguration1 and FeignClientConfiguration2 classes with the @Configuration annotation, they'll be picked up "globally" for the Spring context which essentially means those beans relevant for Feign will be applied to all Feign clients.

I see you specified the configuration attribute on your @FeignClient annotation but that won't "undo" the global configuration.

The way to go is to remove the @Configuration annotation from FeignClientConfiguration1 and FeignClientConfiguration2 and use the @FeignClient configuration attribute only.

I fell into a similar situation recently and after pulling my hair for a long time and debugging, this is how I could make it work. First of all, create a generic converter. This code is in Kotlin:

You can get the status by calling e.status() and then you can switch-case the status and get a message based on that. You could also build a Map of and get the message by status. To read about FeignException more kindly visit https://github.com/OpenFeign/feign/blob/master/core/src/main/java/feign/FeignException.java

And it is strongly advisable to be specific about what you catch:

Retryer was removed from Reactive client. You should use ReactiveRetryPolicy

Using --data-urlencode curl option, you are adding a parameter to the request's body. In your Kotlin code, you are not passing the same data in the request's body, but in the headers.

What you should do (to mimic postman behavior) is to pass grant_type, client_id, client_secret in the request body by using BodyInserters, like this:

It was a timeout issue. The site does answer, but much slower than it does when I connect from my local network.

Increasing the maximum lambda function timeout solved the issue.

It seems the property

feign.hystrix.enabled=true

is changed to

feign.circuitbreaker.enabled=true