[
https://issues.apache.org/jira/browse/NIFI-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490776#comment-15490776
]
Oleg Zhurakousky edited comment on NIFI-2774 at 9/14/16 3:54 PM:
-----------------------------------------------------------------
[[email protected]] it will actually be handled with local TX where there
will be explicit commits and rollbacks. More reliable and easier to follow. The
fix is already in place, just adding tests to validate the behavior. I will
also add more details to this JIRA once completed.
Thank you for pointing this out!
was (Author: ozhurakousky):
[[email protected]] it will actually be handled with local TX where there
will be explicit commits and rollbacks. More reliable and easier to follow. The
fix is already in place, just adding tests to validate the behavior
Thank you for pointing this out!
> 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)
