[EnMasse] Publishing to specific topic and subscribing with wildcard leads to growing queue/topic

Bob Claerhout bob.claerhout at aloxy.io
Tue Jul 30 09:32:51 UTC 2019


Rob,

Sorry, you're correct. The address is in fact a topic:
[cid:part1.59EC1C82.6E4E5B9F at aloxy.io]

Best regars,
Bob

On 7/30/19 11:28 AM, Rob Godfrey wrote:
I'm a little confused - this may just be imprecise use of language, but you say: "Eclipse-ditto is publishing messages to a *queue* called "gw/tenant/tenant:device" ", and then you talk about the backend service subscribing with a (topic) wildcard.

If there is a queue then it will receive all messages sent to that (precise) address.

A consumer subscribing to a wildcard is essentially setting up a second queue which will receive all messages that match the pattern (but will not receive messages that are already in the specific queue, prior to the subscription).

Is the address supposed to represent a queue (with the associated guaranteed delivery semantics) or a topic (in which case it is expected that messages sent when there are no consumers will be discarded)?

-- Rob

On Tue, 30 Jul 2019 at 11:18, Bob Claerhout <bob.claerhout at aloxy.io<mailto:bob.claerhout at aloxy.io>> wrote:
Hi,

While setting up prometheus to monitor our installation, I noticed the "artemis_message_count" on a specific address is growing while I am subscribed to this address using a wildcard.
To be more specific:
Eclipse-ditto is publishing messages to a queue called "gw/tenant/tenant:device". A backend service (python) is subscribed to "gw/#".
In prometheus, I'm getting following artemis_message_counts:
[cid:part3.B900F5CD.441B7019 at aloxy.io]

When I look at the metric "artemis_consumer_count", following records are shown:
[cid:part4.B67117D3.28CAAC3B at aloxy.io]

Any idea on how to prevent the queue from building up?

Best regards
[cid:part5.BC6684C3.A2070D3F at aloxy.io]  Bob Claerhout
Software developer
M +32 479 34 84 92
The Beacon, Sint-Pietersvliet 7, 2000
Antwerp
bob.claerhout at aloxy.io<mailto:bob.claerhout at aloxy.io> | www.aloxy.io<http://www.aloxy.io>
_______________________________________________
enmasse mailing list
enmasse at redhat.com<mailto:enmasse at redhat.com>
https://www.redhat.com/mailman/listinfo/enmasse


--
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com<http://www.de.redhat.com/>,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: ,Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190730/2bf1062b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pjligbpiifmlpkpm.png
Type: image/png
Size: 3940 bytes
Desc: pjligbpiifmlpkpm.png
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190730/2bf1062b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: peihckpcocfdfmcj.png
Type: image/png
Size: 50736 bytes
Desc: peihckpcocfdfmcj.png
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190730/2bf1062b/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bagmoinhepbbjljp.png
Type: image/png
Size: 26943 bytes
Desc: bagmoinhepbbjljp.png
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190730/2bf1062b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mijgimmamimbonlh.png
Type: image/png
Size: 6330 bytes
Desc: mijgimmamimbonlh.png
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190730/2bf1062b/attachment-0003.png>


More information about the enmasse mailing list