RabbitMQ reactive messaging. routing-keys configuration parameter doesn't affect incoming message processing.

[andreiyusupau]

Describe the bug

I'm using same Rabbit MQ queue and publish messages to the exchange for this queue with different routing-keys (and different structure).

Expected behavior

I expect that methods annotated with @Incoming should handle messages only with routing-keys specified in mp.messaging.incoming.<channel-name>.routing-keys

Actual behavior

@Incoming doesn't consider configured routing-keys, and messages are handled by both handlers distributing by round-robin principle.

How to Reproduce?

mp:
  messaging:
    incoming:
      foo:
        connector: smallrye-rabbitmq
        exchange:
          name: example.exchange
        queue:
          name:  example.queue
        routing-keys: example.queue.foo
      bar:
        connector: smallrye-rabbitmq
        exchange:
          name: example.exchange
        queue:
          name: example.queue
        routing-keys: example.queue.bar

    @Blocking
    @Incoming("foo")
    void onFoo(Message<Foo> message) {
        //do something
    }

    @Blocking
    @Incoming("bar")
    void onBar(Message<Bar> message) {
        //do something
    }

Output of uname -a or ver

Microsoft Windows [Version 10.0.26100.4061]

Output of java -version

Corretto 21.0.6

Quarkus version or git rev

3.22.1

Build tool (ie. output of mvnw --version or gradlew --version)

gradle 8.12

Additional information

Is there some sort of misconfiguration? Or should I have only 1 handler (@Incoming) and handle messages with different methods based on routing-key in metadata manually?

[quarkus-bot]

/cc @cescoffier (reactive-messaging), @ozangunalp (reactive-messaging), @radcortez (config)

[ozangunalp]

The routing-keys configuration for incoming channels is used in binding the RabbitMQ queue (where messages are consumed from) to the exchange (where messages are sent).

If in the broker, these bindings to the consumed queue are different, or queue/exchange declarations are disabled, consumer can consume messages with different routing-keys.

Hope this is clear.

[andreiyusupau]

@ozangunalp Sorry, but I don't think that it answers my question.
If my setup is correct, I expected that corresponding methods are invoked for different routing keys. If such config is not working, then I think it should be validated on Quarkus startup.

[ozangunalp]

If my setup is correct, I expected that corresponding methods are invoked for different routing keys.

I am not a RabbitMQ expert, but I think you can do that with different queues, not the same queue.

If such config is not working, then I think it should be validated on Quarkus startup.

It is not feasible to verify connector-specific channel properties, and the configuration's intent may not always be clear.

Hope this answers your question.