spring-cloud / spring-cloud/spring-cloud-commons
Don't throw IllegalStateException when no instances are available
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Once it comes out of a RestTemplate it should be a RestClientException, preferably a ResourceAccessException, so it can be handled consistently.
At the moment it is annoying to deal with.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the RestTemplate boundary where an IllegalStateException is currently exposed when no instances are available. Trace how that failure is propagated and compare it with RestClientException and ResourceAccessException handling. Done means callers receive a consistent RestClientException, preferably a ResourceAccessException, for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100