Develop Reference

Spring Boot Application shown as UNKNOWN in Eureka server

I'm running an application with Spring (as Discovery Client app), also have a Discovery Server with Eureka, and Spring Cloud Config Server. When the client app is started it's registered as "UNKNOWN" in Eureka, despite its status is set to"UP", isn't able to get the properties from the configuration server.
Client App, Eureka server,and Config Server Spring Boot Version: 2.4.2
Client bootstrap.properties:
spring.application.name=config-client-app
spring.cloud.config.discovery.enabled=true
eureka.client.service-url.defaultZone=http://localhost:8761/eureka
eureka.instance.instance-id=${spring.application.name}
Client application.properties file:
logging.level.=debug
server.port=8900
eureka.client.healthcheck.enabled=true
Client Application Class:
#SpringBootApplication
#EnableDiscoveryClient
#RestController
public class ConfigClientAppApplication {
public static void main(String[] args) {
SpringApplication.run(ConfigClientAppApplication.class, args);
}
}
Eureka Serverproperties file:
spring.application.name=discovery-server
server.port=8761
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false
Eureka Application class:
#EnableEurekaServer
#SpringBootApplication
public class DiscoveryServerApplication {
public static void main(String[] args) {
SpringApplication.run(DiscoveryServerApplication.class, args);
}
}
The log info:
restartedMain] c.n.discovery.InstanceInfoReplicator : InstanceInfoReplicator onDemand update allowed rate per min is 4
2021-02-09 16:02:50.388 INFO 2845 --- [ restartedMain] com.netflix.discovery.DiscoveryClient : Discovery Client initialized at timestamp 1612904570388 with initial instances count: 1
2021-02-09 16:02:50.390 INFO 2845 --- [ restartedMain] o.s.c.n.e.s.EurekaServiceRegistry : Registering application UNKNOWN with eureka with status UP
2021-02-09 16:02:50.391 INFO 2845 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : Saw local status change event StatusChangeEvent [timestamp=1612904570391, current=UP, previous=STARTING]
2021-02-09 16:02:50.391 INFO 2845 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_UNKNOWN/192.168.10.22:8900: registering service...
2021-02-09 16:02:50.391 WARN 2845 --- [ restartedMain] c.n.discovery.InstanceInfoReplicator : Ignoring onDemand update due to rate limiter
2021-02-09 16:02:50.393 INFO 2845 --- [ restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8900 (http) with context path ''
2021-02-09 16:02:50.394 INFO 2845 --- [ restartedMain] .s.c.n.e.s.EurekaAutoServiceRegistration : Updating port to 8900
2021-02-09 16:02:50.413 INFO 2845 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_UNKNOWN/192.168.10.22:8900 - registration status: 204

I am using Spring cloud version
<spring-cloud.version>2021.0.5</spring-cloud.version>
and spring boot version
<version>2.7.5</version>
In application.properties, add the following lines to resolve the error:
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false
By default, the Eureka Server registers itself into the discovery. The following 2 lines will tell eureka server that there is only one eureka server present in this context.
in the absence of these, our Eureka Server will try to find and register itself on other Eureka Servers in the context and throw a discovery client exception. i.e our own system.
If you encounter the below errors after adding the above properties only you need to add the below properties.
We must add this to the properties, if configuration is not required.
spring.cloud.config.enabled=false
Otherwise application will throw below exception.
No spring.config.import property has been defined
(or) If you have a other server, such as any configuration server we can add this optional server configuration to application.properties,
spring.config.import=optional:configserver: Your server url
Spring Cloud Config provides server and client-side support for
externalized configuration in a distributed system

how can i create a camel webcocket client? Suggest some reference examples

I am trying to create a websocket client using camel.. Can we implement it using atmosphere websocket.I have referred the document in camel official site. Could you please provide some reference examples on to create a websocket client?
I also tried using ahc with the below code, and the server gets started with the below log,
but i get no response on the client side where the server is continuously sending data
from("ahc-ws://localhost:8180/receive/public")
.log(">>> Message received from WebSocket Client : ${body}")
.transform().simple("${body}${body}");```
Starting CamelMainRunController to ensure the main thread keeps running
2020-04-09 05:40:58.619 INFO 7636 --- [ main] o.a.camel.component.ahc.ws.WsEndpoint : Reconnecting websocket: ws://localhost:8180/ws/recieve/public
2020-04-09 05:40:58.636 INFO 7636 --- [inRunController] org.apache.camel.main.BaseMainSupport : Using properties from classpath:application.properties;optional=true
2020-04-09 05:41:00.309 INFO 7636 --- [ main] o.a.c.impl.engine.AbstractCamelContext : Route: route1 started and consuming from: ahc-ws://localhost:8180/ws/recieve/public
2020-04-09 05:41:00.325 INFO 7636 --- [ main] o.a.c.impl.engine.AbstractCamelContext : Total 1 routes, of which 1 are started
2020-04-09 05:41:00.326 INFO 7636 --- [ main] o.a.c.impl.engine.AbstractCamelContext : Apache Camel 3.1.0 (CamelContext: camel-1) started in 3.845 seconds
2020-04-09 05:41:00.417 INFO 7636 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
2020-04-09 05:41:00.429 INFO 7636 --- [ main] c.w.server.WebsocketClientApplication : Started WebsocketClientApplication in 60.888 seconds (JVM running for 66.527)

HttpClientException : Request Failure

Whenever I run my application, I'm getting the connection request failure exception. The application tries to hit the URL and end up with connection failure.
I have tried the same on Postman. It is giving me 200: OK.
I have the proxy and port as well. How to use it in our spring boot application. Whenever the application runs it should take the respective proxy and port.
I'm attaching here the logs:
creating event for user 0852 for campaign source TEST at stage INITIAL_LANDING
creating event for user 0852 for campaign source TEST at stage CLICK_DEMO
2019-07-19 15:15:39.680 INFO 49560 --- [nio-9898-exec-8] o.a.http.impl.client.DefaultHttpClient : I/O exception (java.net.SocketException) caught when connecting to {s}->https://pi-collector-dev.tr-corporate-nonprod.aws-int.thomsonreuters.com:443: Connection reset
2019-07-19 15:15:39.683 INFO 49560 --- [nio-9898-exec-8] o.a.http.impl.client.DefaultHttpClient : Retrying connect to {s}->https://pi-collector-dev.tr-corporate-nonprod.aws-int.thomsonreuters.com:443
2019-07-19 15:15:49.302 INFO 49560 --- [nio-9898-exec-8] o.a.http.impl.client.DefaultHttpClient : I/O exception (java.net.SocketException) caught when connecting to {s}->https://pi-collector-dev.tr-corporate-nonprod.aws-int.thomsonreuters.com:443: Connection reset
2019-07-19 15:15:49.304 INFO 49560 --- [nio-9898-exec-8] o.a.http.impl.client.DefaultHttpClient : Retrying connect to {s}->https://pi-collector-dev.tr-corporate-nonprod.aws-int.thomsonreuters.com:443
2019-07-19 15:15:58.904 INFO 49560 --- [nio-9898-exec-8] o.a.http.impl.client.DefaultHttpClient : I/O exception (java.net.SocketException) caught when connecting to {s}->https://pi-collector-dev.tr-corporate-nonprod.aws-int.thomsonreuters.com:443: Connection reset
2019-07-19 15:15:58.906 INFO 49560 --- [nio-9898-exec-8] o.a.http.impl.client.DefaultHttpClient : Retrying connect to {s}->https://pi-collector-dev.tr-corporate-nonprod.aws-int.thomsonreuters.com:443
2019-07-19 15:16:08.665 ERROR 49560 --- [nio-9898-exec-8] c.t.providers.persistent.InMemoryQueue : Failed to push events to destination.

Spring Cloud Cannot Load Config

I deployed this Spring application]1 on a kubernetes cluster with kompose up. Once it was deployed, the pods for a number of the services would enter a CrashLoopBackoff state. The services I've had problems with are the account service, monitoring service, notification service, and statistics service. It appears that when the services start up, they run into the following error:
2017-11-15 22:10:52.857 INFO 1 --- [ main] c.p.monitoring.MonitoringApplication : Started MonitoringApplication in 0.511 seconds (JVM running for 8.579)
2017-11-15 22:10:52.882 INFO 1 --- [ main] o.s.c.s.b.r.RabbitMessageChannelBinder : declaring queue for inbound: springCloudHystrixStream.anonymous.oCdNGHmBRPO_Z3LMusKS2Q, bound to: springCloudHystrixStream
2017-11-15 22:11:52.953 WARN 1 --- [ main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'outputBindingLifecycle'; nested exception is org.springframework.context.ApplicationContextException: Failed to start bean 'inputBindingLifecycle'; nested exception is org.springframework.amqp.AmqpIOException: java.net.SocketTimeoutException: connect timed out
The full log can be found here. Any help is greatly appreciated. I assume this is a Spring/Java related issue but it may be a Kubernetes related issue as well given that the application was designed to run on docker swarm.

Consul and Spring Boot services in Docker - not deregistering

So we have Java microservices written with Spring-Boot, using Consul for service discovery and config management and running in Docker containers. All of it is working, but when a container dies or a service restarts the old service-id never goes away in Consul and the service forever after shows as "Failing" in the Consul UI, even though the new container has registered and shows all Green.
We are not using heartbeat - but I cannot find much documentation on what the difference between heartbeat and healthcheck are for Consul.
Here's my bootstrp.yml
spring:
application:
name: my-service
cloud:
config:
enabled: false
consul:
host: ${discovery.host:localhost}
port: ${discovery.port:8500}
config:
watch:
wait-time: 30
delay: 10000
profile-separator: "-"
format: FILES
discovery:
prefer-ip-address: true
instanceId: ${spring.application.name}:${spring.application.instance_id:${random.value}}
There are other settings to enable heartbeat, but the docs say something about this putting more stress on the Consul cluster.
Has anyone managed to get Consul and Spring Boot/Docker services to actually de-register automatically? It actually doesn't cause any real problems, but it makes the Consul UI pretty useless to actually monitor for up/down services.

Consul doesn't automatically deregister services.
See https://groups.google.com/forum/#!topic/consul-tool/slV5xfWRpEE for the hint about the same question. According to that thread you need to either update the config or perform an Agent API call. Since the agent is the source of truth, you shouldn't try to update via Catalog API. See GitHub for details. They also mention at the Google group that you don't necessarily have to deregister services if the node goes down gracefully, but that doesn't seem to be your use case.
Please have a look at Consul not deregistering zombie services for hints about automating the service de-registration using either the api or tools like registrator.

You have mentioned you are using a docker container to run the microservice. Are you trapping the SIGTERM in your entrypoint script in docker container ? If a SIGTERM is sent, the boot application will get it and you will see the below log showing that the microservice is deregistering with Consul.
2017-04-27 09:20:19.854 INFO 6852 --- [on(6)-127.0.0.1] inMXBeanRegistrar$SpringApplicationAdmin : Application shutdown requested.
2017-04-27 09:20:19.857 INFO 6852 --- [on(6)-127.0.0.1] ationConfigEmbeddedWebApplicationContext : Closing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext#afb5821: startup date [Thu Apr 27 09:20:00 EDT 2017]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext#130c12b7
2017-04-27 09:20:19.859 INFO 6852 --- [on(6)-127.0.0.1] o.s.c.support.DefaultLifecycleProcessor : Stopping beans in phase 2147483647
2017-04-27 09:20:19.863 INFO 6852 --- [on(6)-127.0.0.1] o.s.c.support.DefaultLifecycleProcessor : Stopping beans in phase 0
2017-04-27 09:20:19.863 INFO 6852 --- [on(6)-127.0.0.1] o.s.c.c.s.ConsulServiceRegistry : Deregistering service with consul: xxxxxxxxxxxxx
This blog post discusses this.