[
https://issues.apache.org/jira/browse/NIFI-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490669#comment-15490669
]
Christopher McDermott edited comment on NIFI-2774 at 9/14/16 3:14 PM:
----------------------------------------------------------------------
[~joewitt], this means 0.x will not be able to provide lossless operation.
Some us are fixed to the 0.x line for some time. Yes, the GetJMSQueue processor
on 0.x provides the lossless ACK functionality but that processor has several
other bugs which makes it unusable. Those bugs were not fixed because the
reasoning went that GetJMSQueue was being deprecated in favor of ConsumeJMS.
Since the 0.x code is very close to the 1.x code in this area it should be
little extra work to make pull the 1.x fix onto the 0.x branch.
was (Author: ch...@mcdermott.net):
[~joewitt], this means 0.x will not be able to provide lossless operation.
Some us are fixed to the 0.x line for some time. Yes, the GetJMSQueue processor
on 0.x provides the lossless ACK functionality that that processor has several
other bugs which makes it unusable. Those bugs were not fixed because the
reasoning went that GetJMSQueue was being deprecated in favor of ConsumeJMS.
Since the 0.x code is very close to the 1.x code in this area it should be
little extra work to make pull the 1.x fix onto the 0.x branch.
> 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
> 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)
