[ https://issues.apache.org/jira/browse/NIFI-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562581#comment-15562581 ]
ASF GitHub Bot commented on NIFI-2774: -------------------------------------- Github user olegz commented on the issue: https://github.com/apache/nifi/pull/1036 @mosermw all PR comments are addressed > 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: 1.0.0, 0.7.0 > Reporter: Christopher McDermott > Assignee: Oleg Zhurakousky > Priority: Critical > Fix For: 1.1.0, 0.8.0 > > Attachments: 2774.patch > > > 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)