search

noodlefrenzy / node-amqp10

amqp10 is a promise-based, AMQP 1.0 compliant node.js client
MIT License
134 stars 56 forks source link

Question: Is there a way to receive the information of wildcards of a queue? #366

Open jcanadilla opened 6 years ago

jcanadilla commented 6 years ago

Hello,

I am developing a message processor using this library. Next, I explain that I am trying to get. I am using ActiveMQ as a broker and I send messages with MQTT to the broker. Then, the broker puts all MQTT messages in a queue that I am trying to read.

When I send messages to MQTT topic I write: (Example) house/kitchen/fridge/temperature And then I read from AMQP queue with wildcards like that: house.kitchen.*.* My code can read without problem from queue and I receive a message with 5 properties. One of them is properties that has a field to. This property is a string like: "queue://house.kitchen.*.*". I mean that I can't get the queue name without wildcards. I wish I could get something like that: "queue://house.kitchen.fridge.temperature".

So, is there a way to receive the information of wildcards of a queue?

Thank you so much!

amarzavery commented 6 years ago

There is no active development happening in this library. I would recommend using https://github.com/amqp/rhea. It is well supported and is being actively developed.

jcanadilla commented 6 years ago

Hi @amarzavery thank you so much for your response.

I have been searching a solution to this issue with my team and we have found which is the bug. This is a bug of ActiveMQ so rhea (actually) has same problem (confirmed).

Only for somebody that have the same problem: https://issues.apache.org/jira/browse/AMQ-6972

I think that this issue can be closed.

danlangford commented 6 years ago

@noodlefrenzy or @mbroadst can you verify the claim made by @amarzavery? is this library in fact being no longer developed and supported? or is it just that the primary protocol work is done and there hasnt been much work needed on it for a bit?

noodlefrenzy commented 6 years ago

Hey @danlangford, TL;DR version is yes.

We'd transitioned development to @amarzavery and team because we could no longer support it, and they've been transitioning their own code to rhea so have stopped maintaining this. We wrote this before rhea existed and have always been a great admirer of that library since it started - in fact, our last major revision adopted many of their ideas.