[
https://issues.apache.org/jira/browse/ARTEMIS-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254738#comment-17254738
]
Justin Bertram commented on ARTEMIS-2897:
-----------------------------------------
bq. The slow consumer detection works only for the non-durable cases...
That's not true. The documentation just uses the JMS non-durable subscriber as
an example. Slow-consumer detection works for _any_ consumer on _any_ queue.
bq. ...disconnecting and discarding messages for the slow consumers.
The consumer _can_ be disconnected in which case if the consumer is a JMS
non-durable subscriber then the messages will be discarded. However, the broker
can also be configured to just send a notification message. Furthermore, for
other use-cases which don't include non-durable JMS subscribers the messages
won't be discarded if the consumer is disconnected.
bq. For the selectors, an old story, we had other designs too, but the higher
perf non-selectors design failed because the clients prioritize ad-hoc
flexibility provided by selectors over the higher perf.
I'm not clear on what you're saying here. For what it's worth, I wasn't
necessarily recommending a non-selector design. I was saying that queues with
selectors (e.g. in the case of JMS subscribers) is much more efficient than
consumers with selectors.
> Metrics: a queue meter matching management.QueueControl.getFirstMessageAge()
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-2897
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2897
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.14.0
> Reporter: Petr Kuzel
> Priority: Major
>
> The micrometer-instrumentation of the broker queues lacks a gauge for the
> oldest message in the queue.
>
> Could you implement the "first.message.age.ms" meter for queues, please?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
