[
https://issues.apache.org/jira/browse/NIFI-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493346#comment-15493346
]
ASF GitHub Bot commented on NIFI-2774:
--------------------------------------
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/1022
NIFI-2774 changed the default ACK mode to CLIENT
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-2774
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1022.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1022
----
commit a9a4d2efefe99ecefa14f2b502a13c34545f19b5
Author: Oleg Zhurakousky <[email protected]>
Date: 2016-09-15T13:33:27Z
NIFI-2774 changed the default ACK mode to CLIENT
----
> 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, 1.1.0, 0.8.0
> Reporter: Christopher McDermott
> Assignee: Oleg Zhurakousky
> 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)
