[ http://jira.jboss.com/jira/browse/JBESB-831?page=comments#action_12372401 ] Kurt Stam commented on JBESB-831: --------------------------------- The DLQ is not used to redelivery (the RDLVR is). So once it is in the DLQ is truly dead. I had thought it'd be a manual process to empty the DLQ, but I'm happy to add a button somewhere. Where would you like the button? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-831?page=comments#action_12372404 ] Mark Little commented on JBESB-831: ----------------------------------- No, my bad: I meant the redeliver queue, not the DLQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-831?page=all ] Mark Little updated JBESB-831: ------------------------------ Description: It would be useful for certain applications to be able to remove messages from the RDLVR even if they were automatically added by the ESB. For example, suppose that the ESB adds a message to the RDLVR because the service was down. The application knows this and most of the time it's fine. However, in some situations (specifically in the async case) it may use the RDLVR as a backup to it's own application level retries, e.g., trying to do something else to compensate for the failure to deliver. If this "something else" fails, then the RDLVR redelivery is good. If it succeeds, it may not be necessary (or wise) to let the redelivery from the RDLVR go ahead. (was: It would be useful for certain applications to be able to remove messages from the DLQ even if they were automatically added by the ESB. For example, suppose that the ESB adds a message to the DLQ because the service was down. The application knows this and most of the time it's fine. However, in some situations (specifically in the async case) it may use the DLQ as a backup to it's own application level retries, e.g., trying to do something else to compensate for the failure to deliver. If this "something else" fails, then the DLQ redelivery is good. If it succeeds, it may not be necessary (or wise) to let the redelivery from the DLQ go ahead.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira