nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Zhurakousky (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-2774) ConsumeJMS processor losses messages on NiFi restart
Date Thu, 15 Sep 2016 13:40:20 GMT

     [ https://issues.apache.org/jira/browse/NIFI-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Zhurakousky updated NIFI-2774:
-----------------------------------
    Status: Patch Available  (was: Open)

> 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
>            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)

Mime
View raw message