[
https://issues.apache.org/jira/browse/ARTEMIS-3401?focusedWorklogId=627802&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-627802
]
ASF GitHub Bot logged work on ARTEMIS-3401:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Jul/21 14:44
Start Date: 26/Jul/21 14:44
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3670:
URL: https://github.com/apache/activemq-artemis/pull/3670#issuecomment-886766248
Inspecting the messages for `Message.HDR_ORIGINAL_ADDRESS` *might* work. I'm
not sure if that header is stripped when the message is actually retried so you
might encounter a weird situation where messages on the original queue can be
retried.
I'm not sure how using `getAddressSettingsAsJSON` would work here as there's
no "reverse lookup" where you can submit a `dead-letter-address` value and get
back the address names which match. I think you'd have to do some kind of brute
force search by first invoking `getAddressNames` and then taking every
individual address name and using `getAddressSettingsAsJSON` to see if
`dead-letter-address` or `expiry-address` matched the value you're looking for.
Also, there's the complication of auto-created dead-letter and expiry resources
which use a prefix and/or suffix.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 627802)
Time Spent: 0.5h (was: 20m)
> Support dead-letter and expiry identification on the web console via regex
> --------------------------------------------------------------------------
>
> Key: ARTEMIS-3401
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3401
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently dead-letter and expiry addresses can only be identified on the web
> console if they perfectly match a configurable string value (i.e. {{DLQ}} and
> {{ExpiryQueue}} by default respectively). However, lots of users have
> multiple dead-letter and expiry resources which follow the same naming
> pattern. The web console should support using a regular expression so all of
> these addresses can be properly identified.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
