nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-2774) ConsumeJMS processor losses messages on NiFi restart
Date Mon, 19 Sep 2016 19:28:20 GMT


ASF GitHub Bot commented on NIFI-2774:

Github user olegz commented on the issue:
    @ckmcd PR comments addressed with few minor improvements.

> ConsumeJMS processor losses messages on NiFi restart
> ----------------------------------------------------
>                 Key: NIFI-2774
>                 URL:
>             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

View raw message