Closed chlegou closed 2 months ago
This is related to https://github.com/spring-cloud/spring-cloud-netflix/issues . When backend service is not connectable, it could be treated as internal error if configuration is wrong. 404 could be misleading.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
Hi there, i'm running 3 apps jhipster (no registry) gateway and 2 microservices (No Eureka) in docker containers. also, i'm having a route detector filter provided by jHipster. link:
When the microservice is running in a docker container and linked or not linked in zuul routes in yml configs, it's working fine.
but when the microservice docker container is not working, the gateway fails with 500 HTTP code. i tried to intercept it from the filter but with no luck. here is the output:
as i have linked the exception body, i recommend avoiding this 500 error, and return 404 not found service instead.
Thanks.