spring-cloud / spring-cloud/spring-cloud-bus
Bus Refresh Returns Empty Keys in Logs Despite Client Property Update - RefreshListener: Keys refreshed []
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 445
- Forks
- 246
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 5
Description
Hi, I have a small project (link below) using Spring Cloud Config (version 2023.0.3 - Walnut).
This project has two modules:
-
Server (Config Server)
-
Client (Consumes properties via JDBC)
When I update any property in the database and call the /actuator/busrefresh endpoint, the client properties update correctly, but the server logs show an empty array.
Sample:
In this project, I’m using the JDBC strategy with Kafka for the bus refresh.
Everything is explained in the README file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction project and its README; run the two-module JDBC client/server setup, update a property, and call /actuator/busrefresh. Compare the refreshed client properties with the server's RefreshListener log showing [] to identify the scope of the bug; done when the log accurately reports refreshed keys while the existing refresh still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, spring, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100