Justin Bertram

> I need to find out if there's an old message in a queue that's been there for longer than a specified interval, and I'm not allowed to use DLQs...

> or... also I would be okay on adding a metric for number of scheduled messages... We already have that. It's called `scheduledCount`.

> Currently, this basically means to pause the queue, because the GUI doesn't display messages-in-flight. There **is** a management method which shows details of in-flight messages. It's called `listDeliveringMessagesAsJSON`. That...

> ...if this was an operation instead of an attribute, then you wouldn't have the issue of scans from JMX providers, right? @clebertsuconic, that would be _much_ better, but I...

After thinking about it more I haven't come up with any good alternatives. I'm OK with merging this now.

This is an interesting improvement which I think has some merit. However, I have two concerns: - This changes the default behavior of every divert. This may break existing users...

You're right that the `auto-create-*` configs in the `address-settings` apply here. The problem is that they don't apply to this use-case _right now_, and this commit changes this fact which...

How is this related to https://issues.apache.org/jira/browse/ARTEMIS-4045 (i.e. the Jira referenced in the PR title)?

Is this related to https://issues.apache.org/jira/browse/ARTEMIS-3042? The PR's title seems to correspond. If it is related please include the Jira in the commit message. If not, please create a Jira for...

It's not clear to me how your changes are directly related to https://issues.apache.org/jira/browse/ARTEMIS-3042 aside from just the wording. Your commit is just adding a new Dockerfile which is similar to...