You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2019/10/18 11:26:00 UTC

[jira] [Created] (CAMEL-14083) camel-jms - Consumer with poison message should automatic deal with that

Claus Ibsen created CAMEL-14083:
-----------------------------------

             Summary: camel-jms - Consumer with poison message should automatic deal with that
                 Key: CAMEL-14083
                 URL: https://issues.apache.org/jira/browse/CAMEL-14083
             Project: Camel
          Issue Type: Improvement
          Components: camel-jms
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 3.0.0


Related to CAMEL-14078

When using camel-jms you may have JMS messages that are doomed poison due they cannot be read succesfully, such as JMS payload fails to be read. In those use-cases then currently you have a harder time to make Camel error handler react on that. You can turn off mapJmsMessage and then work with the bare javax.jms.Message object. But out of the box it doesn't do that. So ideally we should add new options that deal with this, and allows you to handle this easily, such as route the message to a DLQ, or if you dont' then it will rollback anyway.





--
This message was sent by Atlassian Jira
(v8.3.4#803005)