spring-cloud / spring-cloud/spring-cloud-bus
spring-cloud-starter-bus-kafka dependency breaks consumer message channel
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 445
- Forks
- 246
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 5
Description
Describe the bug
Spring Boot : 3.1.2
Spring Cloud : 2022.0.4
Application uses spring-cloud-stream-binder-kafka and Kafka consumers in functional style.
Adding the spring-cloud-starter-bus-kafka dependency lead to consumer message channel stop registering.
Removing the dependency, results again in a working application
Logs diff
without dependency:
o.s.i.monitor.IntegrationMBeanExporter : Registering MessageChannel signup-in-0
ConsumerConfig values: client.id = consumer-user1-1
group.id = user1
with dependency:
o.s.i.monitor.IntegrationMBeanExporter : Registering MessageChannel springCloudBusInput
client.id = consumer-anonymous.3c0d339a-2479-46bc-b8ae-77d4e20929a2-1
group.id = anonymous.3c0d339a-2479-46bc-b8ae-77d4e20929a2
Sample
https://github.com/APletenev/microservice_template/tree/Cloud_Stream/idp
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 Cloud_Stream/idp sample application and reproduce startup with and without spring-cloud-starter-bus-kafka. Compare the message-channel registration and Kafka consumer values against the supplied logs; done means the application registers signup-in-0 and uses the expected user1 consumer group while the bus dependency remains present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, spring-boot
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100