Home > Back-end >  Spring cloud start an error
Spring cloud start an error

Time:09-30

ERROR 8824 - [tbeatExecutor - 0] C.N.D.S.T.D.R edirectingEurekaHttpClient: Request execution ERROR

Com. Sun. Jersey. API. Client. ClientHandlerException: java.net.ConnectException: Connection refused: connect
At com. Sun. Jersey. Client. Apache4. ApacheHttpClient4Handler. Handle (ApacheHttpClient4Handler. Java: 187) ~ [jersey - apache - client4-1.19.1. Jar: 1.19.1]
At com. Sun. Jersey. API. Client. Filter. GZIPContentEncodingFilter. Handle (GZIPContentEncodingFilter. Java: 123) ~ [jersey - the client - 1.19.1. Jar: 1.19.1]
At com.net flix. Discovery. EurekaIdentityHeaderFilter. Handle (EurekaIdentityHeaderFilter. Java: 27) ~ [eureka - the client - 1.7.0. Jar: 1.7.0]
At com. Sun. Jersey. API. Client. Client. Handle (652). The client Java: ~ [jersey - the client - 1.19.1. Jar: 1.19.1]
At com. Sun. Jersey. API. Client. That WebResource. Handle (682) that WebResource. Java: ~ [jersey - the client - 1.19.1. Jar: 1.19.1]
At com. Sun. Jersey. API. Client. That WebResource. Access the $200 (74) that WebResource. Java: ~ [jersey - the client - 1.19.1. Jar: 1.19.1]
.

Search on the Internet are added to the register - with - eureka: false fetch - registry: false these two, but with the same fault is this why? What a great god help see what reason!

CodePudding user response:

Registry didn't match well

CodePudding user response:

Change the service name to try camel

CodePudding user response:

Have a look at your client address configuration is wrong, or the service did not start, will appear this mistake

CodePudding user response:

Configuration had local time yesterday also reported that wrong, post configured yml file:
 spring: 
Application:
Name: eureka

Server:
Port: 8761
Use - forward - headers: true

Eureka:
Instance:
The hostname: localhost
Client:
# indicates whether or not to register himself to the Eureka Server, the default is true
RegisterWithEureka: false
# indicates whether or not the registration information from Eureka Server, the default is true
FetchRegistry: false
# Eureka Server access address, service registration and client access to the service registry
ServiceUrl:
DefaultZone: http://localhost:8761/eureka/

Note that semi-colons must have a space and then write a value

CodePudding user response:

Client configuration service address try others, see if there are any problems
 
# configuration had access to the service address
Eureka:
Client:
ServiceUrl:
DefaultZone: http://eureka.didispace.com/eureka/

CodePudding user response:

refer to the sixth floor of dream caring response:
client configuration service address try others, see if there are any problems
 
# configuration had access to the service address
Eureka:
Client:
ServiceUrl:
DefaultZone: http://eureka.didispace.com/eureka/

With others no problem, localhost is not
  • Related