-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wildcard Topics #401
Comments
That will depend on the broker you are using. |
I am using AMQ7 Red Hat Broker |
Use something like 'topic://topic.*' as the source address when creating a subscriber. |
I tried what you told me and I had no luck, this is how the code stays, you think something is missing, make a clarification, I need the messages to be persistent, that's why I add the durable and the shared one because it is in a scalable environment
|
In what way is it not working as you expect? |
I send the publisher and the subscribers do not receive the message,
|
What if you set topic to |
in the publisher or in the subscriber, you decide to put that |
In the publisher |
i.e. topic.* matches topic.foo or topic.bar but not topic (topic.# would match all three) |
I put in the publisher topic://topic.foo I sent the message and no subscriber received it and both subscribers had topic topic://topic.* |
It will be that I have to configure something in the amq red hat |
Can you try the example here: https://github.com/amqp/rhea/blob/main/examples/durable_subscription/publisher.js and https://github.com/amqp/rhea/blob/main/examples/durable_subscription/subscriber.js ? Does that work against your broker? |
I tried and it worked, my question is the following: if I change the topic of the example in the publisher to topic://PRICE.STOCK.* |
Yes |
Hello, good morning, I wanted to know how I can use wildcard with this library since I don't see anything in the documentation, I've tried several variants of code and I can't solve it.
The idea is to be able to send a message to a topic with a wildcard and for this message to be forwarded to all topics with the same wildcard pattern, example:
Wildcard: topic.*
It would have to send the message to all the topics that have that pattern topic1, topic2, etc.
The text was updated successfully, but these errors were encountered: