I have three microservices as follows zuul, eureka and producer. i want to hit /employee in producer service, for client discovery i am using eureka and for proxy i am using zuul. every thing is working fine when running on sts, but on external tomcat its throwing 404. eureka is not appending war name in instance id. instance id: PRO-PF05AWS5.PROFINCHBLR.COM:producer:8082 but it should be PRO-PF05AWS5.PROFINCHBLR.COM:producer:8082/producer here is my code: eureka.war: application.properties
server.port=8081 eureka.client.service-url.defaultZone: http://localhost:8081/eureka/eureka spring.application.name=eureka spring.jmx.default-domain=eureka eureka.client.registerWithEureka=false eureka.client.fetchRegistry=false
zuul.war: application.properties
eureka.client.serviceUrl.defaultZone=http://localhost:8081/eureka/eureka/ server.port=8082 spring.jmx.default-domain=zuul spring.application.name=zuul ribbon.eureka.enabled=false
producer.war: application.properties
eureka.client.serviceUrl.defaultZone=http://localhost:8081/eureka/eureka/
server.port:8082
spring.application.name=producer
server.ssl.enabled=false
eureka.client.enabled=true
Thanks in advance
Comment From: ryanjbaxter
The instaceId has no effect on the hostname registered with the Eureka server. In fact Eureka clients only register host and port and not the path to a particular endpoint, so it is working as expected.
Comment From: xcheng
Did you get this resolved?
Comment From: spencergibb
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
Comment From: RiazShaik79
I am having a similar issue.. I have two micro services as eureka clients deployed on tomcat server. microservice1 is doing a rest call to microservice2. However, eureka discovery is not able to resolve the registered service and it fails with 404. when I deploy microservice 2 as standalone outside. all works okay :(
Comment From: spencergibb
@RiazShaik79 please ask on gitter or stack overflow not closed issues
Comment From: cagrigurakin
same issue.