Kafka Reactive Binder does not work with multiple bindings

When using the Kafka Reactive Binder to consume messages from two different Kafka Cluster the app start fails with onfigReactiveWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context

I have a similar setup like the following:

spring:
  cloud:
    stream:
      binders:
        kafka1:
          type: kafka
          environment:
            spring:
              cloud:
                stream:
                  kafka:
                    binder:
                      brokers: kafka-cluster-1:9092
                      configuration:
                        security.protocol: SSL
                        ssl.truststore.location: /path/to/truststore.jks
                        ssl.truststore.password: yourpassword
        kafka2:
          type: kafka
          environment:
            spring:
              cloud:
                stream:
                  kafka:
                    binder:
                      brokers: kafka-cluster-2:9092
                      configuration:
                        security.protocol: SSL
                        ssl.truststore.location: /path/to/truststore.jks
                        ssl.truststore.password: yourpassword

      bindings:
        input1-in-0:
          destination: topic1
          binder: kafka1
        input2-in-0:
          destination: topic2
          binder: kafka2

and

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-stream</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-stream-binder-kafka-reactive</artifactId>
</dependency>

I tried to add the dependency:

  <dependency>
      <groupId>org.springframework.cloud</groupId>
      <artifactId>spring-cloud-stream-binder-kafka</artifactId>
    </dependency>

so that the configuration works but then the reactive part is ignored and it seems that the messages are consumed on a non reactive thread container-0-C-1 instead of nc-read-local-1 .

Start by reproducing the YAML configuration with two Kafka binders and the spring-cloud-stream-binder-kafka-reactive dependency, then compare it with the non-reactive Kafka binder setup described in the issue. Done means both clusters can be consumed through separate bindings while the reactive consumer remains in use and application startup succeeds.