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.