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

Posted to issues@nifi.apache.org by "Christopher McDermott (JIRA)" <ji...@apache.org> on 2016/09/14 14:23:20 UTC

[jira] [Created] (NIFI-2774) ConsumeJMS processor losses messages on NiFi restart

Christopher McDermott created NIFI-2774:
-------------------------------------------

             Summary: ConsumeJMS processor losses messages on NiFi restart
                 Key: NIFI-2774
                 URL: https://issues.apache.org/jira/browse/NIFI-2774
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 0.7.0, 1.0.0, 1.1.0, 0.8.0
            Reporter: Christopher McDermott
            Priority: Critical
             Fix For: 1.1.0, 0.8.0


ConsumeJMS processor uses auto-acknowledge mode.  Unlike the deprecated GetJMSQueue processor it does not provide a way to specify a different ACK mode (i.e. client-acknowledge.)  Using auto-acknowledge, acknowledges message receipt from JMS *before* the messages are actually added to the flow.  This leads to data-loss on NiFi stop (or crash.)

I believe the fix for this is to allow the user to specify the ACK mode in the processor configuration like is allowed by the GetJMSQueue processor.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)