spring-cloud / spring-cloud/spring-cloud-stream

Application fails to start when using Pulsar binder in multi-binder scenario

Open
#3,013 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

PULSAR-BINDER
Dominant language
Java
Stars
1.1k
Forks
646
Avg merge
2d 3h
Merged PRs (30d)
8

Description

Scenario

A Spring Boot application using SCSt w/ Pulsar binder as input and Kafka binder as an output.

Problem

App fails to start w/ following message:

No qualifying bean of type 'org.springframework.pulsar.core.PulsarAdministration.

Expected Behavior

Application starts with Pulsar as input binder and Kafka as output binder.

Details

The reporting user followed this guide to configure the binders w/ the following yaml:

      binders:
        kafka:
          type: kafka
          (...)
        pulsar:
          type: pulsar
          environment:
            spring:
              cloud:
                stream:
                  pulsar:
                    binder:
                      config:
                        serviceUrl: pulsar://localhost:6650
                        adminUrl: http://localhost:8080

After deleting the environment property from pulsar binder config above, everything is fine, but it disables the possibility of additional configuration at this level.

Original report: https://stackoverflow.com/questions/79046248/springboot-spring-cloud-stream-pulsar-binder-startup-failed

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the binder configuration in the issue and compare it with the multiple-binders guide linked in the report, focusing on the Pulsar binder environment settings. Reproduce the startup failure with Pulsar as input and Kafka as output, and consider the issue done when the application starts while retaining that environment configuration.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.