wildcarded mqtt topic not receiving messages

[ddlenz]

Describe the bug
An MQTT message consumer using 1.5.0.Final does not receive messages when configured with a wildcarded topic, e.g. mp.messaging.incoming.topic-all.topic=topic/+
Works as expected with 1.4.2.Final.

Expected behavior
Output from reproduce case using 1.4.2.Final:

Sending topic one 
Sending topic two 
Receiving message: 1 
Receiving message: 2

Actual behavior
Output from reproduce case using 1.5.0.Final:

Sending topic one 
Sending topic two 

To Reproduce

1. Unzip mqtt-wildcard-issue.zip
2. docker-compose up
3. mvn quarkus:dev

Configuration

# MQTT sink topic one
mp.messaging.outgoing.topic-one.type=smallrye-mqtt
mp.messaging.outgoing.topic-one.topic=topic/one
mp.messaging.outgoing.topic-one.host=localhost
mp.messaging.outgoing.topic-one.port=1883
mp.messaging.outgoing.topic-one.auto-generated-client-id=true

# MQTT sink topic two
mp.messaging.outgoing.topic-two.type=smallrye-mqtt
mp.messaging.outgoing.topic-two.topic=topic/two
mp.messaging.outgoing.topic-two.host=localhost
mp.messaging.outgoing.topic-two.port=1883
mp.messaging.outgoing.topic-two.auto-generated-client-id=true

# MQTT source topic
mp.messaging.incoming.topic-all.type=smallrye-mqtt
mp.messaging.incoming.topic-all.topic=topic/+
mp.messaging.incoming.topic-all.host=localhost
mp.messaging.incoming.topic-all.port=1883
mp.messaging.incoming.topic-all.auto-generated-client-id=true

Environment (please complete the following information):

• Output of uname -a or ver: Darwin NEON-08015 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64
• Output of java -version:
  openjdk version "1.8.0_242"
  OpenJDK Runtime Environment (build 1.8.0_242-b06)
  OpenJDK 64-Bit Server VM GraalVM CE 20.0.0 (build 25.242-b06-jvmci-20.0-b02, mixed mode)
• Quarkus version or git rev: 1.5.0.Final
• Build tool (ie. output of mvnw --version or gradlew --version): Apache Maven 3.6.3

[buehren]

Same problem here!

Did not see this issue before - so I created another project for reproducing the error:
https://github.com/buehren/quarkus-1.5.0-mqtt-wildcard-problem

You can observe the following behaviours:

1. Quarkus 1.4.2-Final works with wildcard in MQTT subscription
2. Quarkus 1.5.0-Final does NOT work with wildcard (ERROR)
3. Quarkus 1.5.0-Final works without wildcard

[buehren]

It still fails with Quarkus 1.5.1-Final.

To reproduce: https://github.com/buehren/quarkus-1.5.0-mqtt-wildcard-problem

[buehren]

It still fails with Quarkus 1.5.2-Final.

To reproduce: https://github.com/buehren/quarkus-1.5.0-mqtt-wildcard-problem (updated to 1.5.2)

[buehren]

It seems that this bug was introduced in smallrye-reactive-messaging 2.0.3. It is planned to be fixed in 2.2.0: smallrye/smallrye-reactive-messaging#615

[cescoffier]

Has been fixed in Quarkus 1.6.