activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Naseef (JIRA)" <>
Subject [jira] [Assigned] (AMQ-4175) Adding a retry-button
Date Fri, 14 Feb 2014 21:44:20 GMT


Arthur Naseef reassigned AMQ-4175:

    Assignee: Arthur Naseef

> Adding a retry-button
> ---------------------
>                 Key: AMQ-4175
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: webconsole
>            Reporter: Torbjørn Skyberg Knutsen
>            Assignee: Arthur Naseef
>            Priority: Minor
>         Attachments: browse.jsp, message.jsp
> In the project I'm working on, we have set up to have one dead-letter queue for each
queue. In the web console of the AMQ 5.3.0 instance that was running up until recently (we
upgraded to 5.7.0), there was a link for "retry" in both the overview of a queue and the overview
of a message. What this did was to move the message to its intended destination, for retrying
failed messages that wound up in a dead-letter queue.
> I could not see this feature in AMQ 5.7.0, and after a bit of investigation, it turned
out that this was added by the people who set up AMQ 5.3.0.
> In my opinion this is a really nice thing to have, specially if you have a large number
of queues. Going through the list of queues and finding the correct one to move to for each
failed message is a lot more work than just clicking a retry-button.
> I'll attach my tweaked versions of browse.jsp and message.jsp, containing the retry button.
If you decide to take it in, it should be generalized a little (right now the prefixes we
set up to use for dead-letter queues and topics are hard-coded). There are also a few minor
tweaks, most notably one that makes sure that the whole queue name is showing in the dropdown
for selecting a queue to move/copy to (having ~80 queues, most with the same prefix in their
name, gave only the four last letters of the queue name to identify it by when it was shortened,
impossible to work with..)

This message was sent by Atlassian JIRA

View raw message