Spring Cloud - Registry Service port customization
19,624
Ok, got it... the label after service-url property (which can be aliased as serviceUrl in YML) is a HashMap KEY, not a property label. So it has to be kept as a Camel Case tag in any ways!
eureka.client.service-url.defaultZone=http://[myIP@]:8787/eureka
![Thomas Escolan](https://lh4.googleusercontent.com/-VrPN_xXn_LQ/AAAAAAAAAAI/AAAAAAAAAAo/2RApUr1suvo/photo.jpg?sz=256)
Author by
Thomas Escolan
Updated on June 21, 2022Comments
-
Thomas Escolan about 2 years
I'd like to customize the Eureka port with Spring Cloud. With the default port below, the services registry sees itself right (within the provided GUI)
spring: application: name: services-registry server: port: 8761 eureka: instance: hostname: localhost nonSecurePort: ${server.port} client: register-with-eureka: true fetch-registry: false service-url: default-zone: http://${eureka.instance.hostname}:${server.port}/eureka/
But if I just change server.port to 8787, no service can register itself, not even the services registry itself.
2017-01-09 16:18:21.584 WARN 17496 --- [nfoReplicator-0] c.n.d.s.t.d.RetryableEurekaHttpClient : Request execution failure 2017-01-09 16:18:21.584 WARN 17496 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_SERVICES-REGISTRY/xxx.org:services-registry:8787 - registration failed Cannot execute request on any known server com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server ... 2017-01-09 16:13:33.299 WARN 17496 --- [nfoReplicator-0] c.n.discovery.InstanceInfoReplicator : There was a problem with the instance info replicator com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server
Can someone explain this issue and save my day? Thanks!
-
Behnam Safari almost 5 yearsOh my God! You are a true life saver man! I spent two days to find it!!!!
-
Feezan Khattak over 2 yearsHow can we find the IP address