thezbyg commented on PR #1198: URL: https://github.com/apache/activemq/pull/1198#issuecomment-2046523027
> So this is just how the broker currently works to handle wildcard subscriptions, since you are publishing to a wildcard topic then any subscription that matches needs to also subscribe tot he wildcard to get that message. Thanks for the explanation. Everything makes sense, except that auto-creation of wildcard topic can also be triggered by a wildcard consumer and results in the same issue. This happens when subscribing to wildcard topic by using STOMP protocol. In the broker code I can see that wildcard topic is not auto-created for wildcard or composite consumer destination: https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L344 No such condition exists in processConsumerControl() method: https://github.com/apache/activemq/blob/e025e443e65d4bd3c2c27f11d6caa7bfbd2c9626/activemq-broker/src/main/java/org/apache/activemq/broker/region/AbstractRegion.java#L694 When using STOMP protocol, processConsumerControl() is called immediately after subscribe and auto-creates the wildcard topic. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
