You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 20, 2024. It is now read-only.
Hi,
I have simple service, that produce messages to Kafka topic using spring cloud stream. The service is added into Consul service discovery. Consul indicate, that the service is randomly failed. Consul use /actuator/health endpoint to indicate if service is in healthy state. Some call to the service return 503 with detail
HTTP GET http://172.31.135.146:9080/actuator/health: 503 Service Unavailable Output:
{
"status":"DOWN",
"binders": {
"status":"DOWN",
"details":{
"kafka":{
"status":"DOWN",
"details":{
"healthIndicator": {
"status":"DOWN",
"details": {
"error":"java.util.ConcurrentModificationException: KafkaConsumer is not safe for multi-threaded access"
}
}
}
}
}
},
....
}
It seems that this happened in case parallel call is done on /actuator/health endpoint.
Using Spring Boot 2.0.3 and Spring Cloud Finchley.RELEASE
The text was updated successfully, but these errors were encountered:
Fixesspring-attic#404
The fix for issue spring-attic#231
added a shared consumer but the consumer is not thread safe. Add synchronization.
Also, a timeout was added to the `KafkaBinderHealthIndicator` but not to the
`KafkaBinderMetrics` which has a similar shared consumer; add a timeout there.
Fixesspring-attic#404
The fix for issue spring-attic#231
added a shared consumer but the consumer is not thread safe. Add synchronization.
Also, a timeout was added to the `KafkaBinderHealthIndicator` but not to the
`KafkaBinderMetrics` which has a similar shared consumer; add a timeout there.
Hi,
I have simple service, that produce messages to Kafka topic using spring cloud stream. The service is added into Consul service discovery. Consul indicate, that the service is randomly failed. Consul use
/actuator/health
endpoint to indicate if service is in healthy state. Some call to the service return 503 with detailIt seems that this happened in case parallel call is done on
/actuator/health
endpoint.Using Spring Boot 2.0.3 and Spring Cloud Finchley.RELEASE
The text was updated successfully, but these errors were encountered: