Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 3 Nov 2017 08:44:00 +0000 (UTC)
From: "Tom Ross (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13115858.1509698590000.140900.1509698640092@Atlassian.JIRA>
In-Reply-To: <JIRA.13115858.1509698590000@Atlassian.JIRA>
References: <JIRA.13115858.1509698590000@Atlassian.JIRA> <JIRA.13115858.1509698590265@jira-lw-us.apache.org>
Subject: [jira] [Created] (ARTEMIS-1497) Destroy message instead of sending
 it to DLQ
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 03 Nov 2017 08:44:04 -0000

Tom Ross created ARTEMIS-1497:
---------------------------------

             Summary: Destroy message instead of sending it to DLQ
                 Key: ARTEMIS-1497
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1497
             Project: ActiveMQ Artemis
          Issue Type: New Feature
          Components: Broker
    Affects Versions: 2.3.0
         Environment: ActiveMQ 2.3
            Reporter: Tom Ross


Customer would like to have an option of destroying certain messages instead of sending them to DLQ in case message processing fails. 

Below is an example of what they think could happen:

{noformat}
public class HelloMDB implements MessageListener {

    MessageDrivenContext ctx;

    @Override
    public void onMessage(Message message) {
        
        try {
            
            doSomeInsertsButThenFailBecauseOfDataThatMakesNoSense();
            
        } catch (UnableToProcessMessageBecauseOfDataThatMakesNoSense e) {
            
            ctx.setRollbackOnly(); // we do not want to commit, because we do not know how many inserts we did before we failed
            
            try {
                message.setBooleanProperty("DESTROY_INSTEAD_OF_GOING_TO_ERROR_QUEUE", true);
            } catch (JMSException ex) {
                throw new RuntimeException("unable to set destroy property", e);
            }
        }
    }
{noformat}

In the case above they would like a message that was a rolled back and tagged with DESTROY_INSTEAD_OF_GOING_TO_ERROR_QUEUE property to be destroyed instead of send to DLQ. If that happens they would like the broker to log that instance in the server log file.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)